Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.00010442733764648438s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0015518665313720703s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.35877561569213867s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.05328202247619629s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00039005279541015625s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.1205673217773438e-05s
INFO | --- Analysis for 0080-3626 took 5.88545036315918s
Availability | SPARQL endpoint availability check for 土地利用图 took 9.369850158691406e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.528559684753418s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 2.86102294921875e-05s
Believability | Calculation of trust value for 土地利用图 took 1.1444091796875e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 5.383363485336304s
Availability | SPARQL endpoint availability check for 113322 took 9.870529174804688e-05s
Availability | VoID file availability check for 113322 took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for 113322 took 1.2749347686767578s
Reputation | Calculation of the PageRank for 113322 took 0.020791053771972656s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.0517578125e-05s
Believability | Calculation of trust value for 113322 took 8.58306884765625e-06s
INFO | --- Analysis for 11 took 8.872097492218018s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.291534423828125e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.00034928321838378906s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.31918883323669434s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.02146625518798828s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.0994415283203125e-05s
Believability | Calculation of trust value for Korepetycje Buki took 7.152557373046875e-06s
INFO | --- Analysis for 12323 took 2.0557165145874023s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06896138191223145s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 1.5293529033660889s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.940696716308594e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.1205673217773438e-05s
INFO | --- Analysis for 2000-us-census-rdf took 7.705681800842285s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.1544978618621826s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.30815649032592773s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 8.821487426757812e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 13.463362455368042s
Availability | SPARQL endpoint availability check for Open Data Web took 16.141936779022217s
Availability | VoID file availability check for Open Data Web took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.32207489013671875s
Reputation | Calculation of the PageRank for Open Data Web took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.2901763916015625e-05s
Believability | Calculation of trust value for Open Data Web took 7.152557373046875e-06s
INFO | --- Analysis for _data.odw.tw took 26.489234685897827s
Availability | SPARQL endpoint availability check for 土地利用 took 4.506111145019531e-05s
Availability | VoID file availability check for 土地利用 took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.500255823135376s
Reputation | Calculation of the PageRank for 土地利用 took 0.021123647689819336s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0010542869567871094s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.600120544433594e-05s
Believability | Calculation of trust value for 土地利用 took 1.2874603271484375e-05s
INFO | --- Analysis for _data1.odw.tw took 4.053659915924072s
Availability | SPARQL endpoint availability check for 土地利用模型 took 0.00010347366333007812s
Availability | VoID file availability check for 土地利用模型 took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.3126184940338135s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.02355360984802246s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0011234283447265625s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 4.57763671875e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.0728836059570312e-05s
INFO | --- Analysis for _data2.odw.tw took 5.632052183151245s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00011205673217773438s
Availability | VoID file availability check for Indian Biodiversity took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.9816303253173828s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020835161209106445s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9087066650390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1682510375976562e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 12.704168558120728s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 0.00013780593872070312s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.5235562324523926s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02374720573425293s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0012743473052978516s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 4.3392181396484375e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.2159347534179688e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 6.375115871429443s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 8.893013000488281e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 1.93977689743042s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.021422386169433594s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.24249267578125e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 1.1920928955078125e-05s
INFO | --- Analysis for A1 took 8.162431955337524s
Availability | SPARQL endpoint availability check for SummerOlympics took 3.929365396499634s
Availability | VoID file availability check for SummerOlympics took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.32742738723754883s
Reputation | Calculation of the PageRank for SummerOlympics took 0.025757312774658203s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0013651847839355469s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 9.179115295410156e-05s
Believability | Calculation of trust value for SummerOlympics took 1.33514404296875e-05s
INFO | --- Analysis for abc took 12.176746845245361s
Availability | SPARQL endpoint availability check for Test_m took 9.059906005859375e-05s
Availability | VoID file availability check for Test_m took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Test_m took 0.6923258304595947s
Reputation | Calculation of the PageRank for Test_m took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for Test_m took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.0040740966796875e-05s
Believability | Calculation of trust value for Test_m took 7.867813110351562e-06s
INFO | --- Analysis for ABC took 3.3836007118225098s
Availability | SPARQL endpoint availability check for my intro took 8.797645568847656e-05s
Availability | VoID file availability check for my intro took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for my intro took 0.33495187759399414s
Reputation | Calculation of the PageRank for my intro took 0.02141094207763672s
Interlinking | Calculation of Degree of Connection for my intro took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for my intro took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for my intro took 3.337860107421875e-05s
Believability | Calculation of trust value for my intro took 1.1920928955078125e-05s
INFO | --- Analysis for abhay_intro took 2.4851932525634766s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.09597373008728027s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.3920161724090576s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02112126350402832s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00011014938354492188s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for abs-linked-data took 4.289667129516602s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 262.085125207901s
Availability | VoID file availability check for Academic Offer of UNL took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.49166226387023926s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.02090311050415039s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.552436828613281e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.2874603271484375e-05s
INFO | --- Analysis for academic-offer-of-unl took 398.3644256591797s
Availability | SPARQL endpoint availability check for AcadOnto took 8.821487426757812e-05s
Availability | VoID file availability check for AcadOnto took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.5555622577667236s
Reputation | Calculation of the PageRank for AcadOnto took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.123283386230469e-05s
Believability | Calculation of trust value for AcadOnto took 1.2159347534179688e-05s
INFO | --- Analysis for acadonto took 5.198665142059326s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.257611989974976s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.5772712230682373s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.31456971168518066s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02208995819091797s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.886222839355469e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for acorn-sat took 35.448856830596924s
Availability | SPARQL endpoint availability check for Addgene took 0.0001246929168701172s
Availability | VoID file availability check for Addgene took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for Addgene took 0.31737804412841797s
Reputation | Calculation of the PageRank for Addgene took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for Addgene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.552436828613281e-05s
Believability | Calculation of trust value for Addgene took 1.1682510375976562e-05s
INFO | --- Analysis for addgene took 14.905825138092041s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 8.869171142578125e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.9204649925231934s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 1.785677433013916s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02180004119873047s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.584426879882812e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.1444091796875e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 13.46177339553833s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.48081254959106445s
Availability | VoID file availability check for AEMET metereological dataset took 0.2878448963165283s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.3178565502166748s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02189946174621582s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for AEMET metereological dataset took 2.86102294921875e-06s
Believability | Calculation of trust value for AEMET metereological dataset took 1.3113021850585938e-05s
INFO | --- Analysis for aemet took 4.6215972900390625s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 0.00010228157043457031s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 1.5986158847808838s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02579665184020996s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0013892650604248047s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 4.744529724121094e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 2.574920654296875e-05s
INFO | --- Analysis for agenda-de-zaragoza took 10.233778476715088s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.04343986511230469s
Availability | VoID file availability check for AgriNepalData took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for AgriNepalData took 1.8147552013397217s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020933151245117188s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.414817810058594e-05s
Believability | Calculation of trust value for AgriNepalData took 1.1444091796875e-05s
INFO | --- Analysis for agrinepaldata took 6.5641374588012695s
Availability | SPARQL endpoint availability check for AGRIS took 262.6931002140045s
Availability | VoID file availability check for AGRIS took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for AGRIS took 0.5499706268310547s
Reputation | Calculation of the PageRank for AGRIS took 0.020868778228759766s
Interlinking | Calculation of Degree of Connection for AGRIS took 2.288818359375e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0011806488037109375s
Interlinking | Calculation of Clustering coefficient for AGRIS took 0.00011873245239257812s
Believability | Calculation of trust value for AGRIS took 1.0013580322265625e-05s
INFO | --- Analysis for agris took 445.10399174690247s
Availability | SPARQL endpoint availability check for AGROVOC took 0.15984654426574707s
Availability | VoID file availability check for AGROVOC took 0.0003952980041503906s
Extra | Recovery of all triples for AGROVOC took 25.88157820701599s
Performance | Total latancy measurement for AGROVOC took 0.4378221035003662s
Amount of data | Number of triples check for AGROVOC took 12.495642900466919s
Interoperability | New terms check for AGROVOC took 3.0136773586273193s
Versatility | Languages check for AGROVOC took 51.59731864929199s
Interpretability | Number of blank nodes check for AGROVOC took 12.747463941574097s
Interpretability | RDF structures check for AGROVOC took 0.0878744125366211s
Versatility | Serialization formats check for AGROVOC took 0.09061050415039062s
Availability | RDF dump link check for AGROVOC took 0.0744171142578125s
License | MR license check for AGROVOC took 0.26577091217041016s
License | HR license check for AGROVOC took 0.37929797172546387s
Amount of data | Number of property check for AGROVOC took 0.09895539283752441s
Understandability | Number of label check for AGROVOC took 39.21367573738098s
Understandability | URI regex check for AGROVOC took 0.17847013473510742s
Understandability | Vocabs check for AGROVOC took 0.09684944152832031s
Verifiability | Authors check for AGROVOC took 0.09701824188232422s
Verifiability | Publishers check for AGROVOC took 0.07371926307678223s
Performance | Throughput check for AGROVOC took 10.43117642402649s
Amount of data | Check the number of entities for AGROVOC took 9.274482727050781e-05s
Verifiability | Contribs. check for AGROVOC took 0.07647299766540527s
Interlinking | sameAs chians check for AGROVOC took 0.08748459815979004s
Interlinking | skos check for AGROVOC took 0.7355852127075195s
Interlinking | skos check for AGROVOC took 0.1337277889251709s
Timeliness | dataset update frequency check for AGROVOC took 0.08574390411376953s
Currency | Creation date check for AGROVOC took 3.987389326095581s
Currency | Modification date check for AGROVOC took 1.5212976932525635s
Rep.Conc. | URIs length for AGROVOC took 35.92515015602112s
Interoperability | New vocabularies check for AGROVOC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.09714913368225098s
Accuracy | Check Functional Property for AGROVOC took 0.09151816368103027s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.09933042526245117s
Accuracy | Check Empty annotation labels for AGROVOC took 19.68356466293335s
Accuracy | Check White space in annotation for AGROVOC took 3.0323984622955322s
Accuracy | Check Datatype consistency for AGROVOC took 4.595822095870972s
Consistency | Disjoint class check for AGROVOC took 0.08106184005737305s
Consistency | Check Misplaced properties for AGROVOC took 10.768903255462646s
Consistency | Check Ontology hijacking for AGROVOC took 20.543394088745117s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.7139759063720703s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 12.456358194351196s
Conciseness | Check Extensional conciseness for AGROVOC took 2.7956175804138184s
Conciseness | Check Intensional conciseness for AGROVOC took 0.09602022171020508s
Security | Sign check for AGROVOC took 0.09728813171386719s
Availability | Check URIs Dereferenciability for AGROVOC took 2230.9580125808716s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.6798522472381592s
Reputation | Calculation of the PageRank for AGROVOC took 0.021769046783447266s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011968612670898438s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 1.2636184692382812e-05s
INFO | --- Analysis for agrovoc took 3882.765694141388s
Availability | SPARQL endpoint availability check for AGROVOC took 8.678436279296875e-05s
Availability | VoID file availability check for AGROVOC took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.6955256462097168s
Reputation | Calculation of the PageRank for AGROVOC took 0.02170538902282715s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0009071826934814453s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 8.130073547363281e-05s
Believability | Calculation of trust value for AGROVOC took 7.295608520507812e-05s
INFO | --- Analysis for agrovoc-skos took 183.03019666671753s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.172396183013916s
Availability | VoID file availability check for Analytics India Magazine took 0.0006229877471923828s
Extra | Recovery of all triples for Analytics India Magazine took 2.211176633834839s
Performance | Total latancy measurement for Analytics India Magazine took 3.1468660831451416s
Amount of data | Number of triples check for Analytics India Magazine took 1.507155179977417s
Versatility | Languages check for Analytics India Magazine took 1.3731443881988525s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.4310705661773682s
Interpretability | RDF structures check for Analytics India Magazine took 1.1999189853668213s
Versatility | Serialization formats check for Analytics India Magazine took 1.0459949970245361s
Availability | RDF dump link check for Analytics India Magazine took 1.1545672416687012s
License | MR license check for Analytics India Magazine took 1.0903615951538086s
License | HR license check for Analytics India Magazine took 1.369431972503662s
Amount of data | Number of property check for Analytics India Magazine took 1.1938796043395996s
Understandability | Number of label check for Analytics India Magazine took 1.1922240257263184s
Understandability | URI regex check for Analytics India Magazine took 2.5292084217071533s
Understandability | Vocabs check for Analytics India Magazine took 0.9571311473846436s
Verifiability | Authors check for Analytics India Magazine took 1.4314665794372559s
Verifiability | Publishers check for Analytics India Magazine took 1.4563477039337158s
Performance | Throughput check for Analytics India Magazine took 15.08924126625061s
Amount of data | Check the number of entities for Analytics India Magazine took 0.00010442733764648438s
Verifiability | Contribs. check for Analytics India Magazine took 1.4220621585845947s
Interlinking | sameAs chians check for Analytics India Magazine took 0.9789745807647705s
Interlinking | skos check for Analytics India Magazine took 0.9305078983306885s
Interlinking | skos check for Analytics India Magazine took 1.061096429824829s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.342712163925171s
Currency | Creation date check for Analytics India Magazine took 2.586428642272949s
Currency | Modification date check for Analytics India Magazine took 2.2944014072418213s
Rep.Conc. | URIs length for Analytics India Magazine took 2.1749093532562256s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.0109727382659912s
Consistency | Disjoint class check for Analytics India Magazine took 1.1460826396942139s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.2456309795379639s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 3.33061146736145s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.0001614093780517578s
Security | Sign check for Analytics India Magazine took 1.1546392440795898s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.46025919914245605s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.021312236785888672s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 7.152557373046875e-07s
Believability | Calculation of trust value for Analytics India Magazine took 1.2636184692382812e-05s
INFO | --- Analysis for AIM took 219.90672636032104s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 260.5722336769104s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.3171510696411133s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02331089973449707s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0016133785247802734s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 4.9114227294921875e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.239776611328125e-05s
INFO | --- Analysis for AISHE took 262.4340229034424s
Availability | SPARQL endpoint availability check for  equipment ontology took 9.107589721679688e-05s
Availability | VoID file availability check for  equipment ontology took 0.0003509521484375s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.31516385078430176s
Reputation | Calculation of the PageRank for  equipment ontology took 0.022404193878173828s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for  equipment ontology took 1.1444091796875e-05s
INFO | --- Analysis for akash took 62.50906562805176s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 1.4956042766571045s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.31297779083251953s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.025540590286254883s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0013904571533203125s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 4.76837158203125e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 1.2636184692382812e-05s
INFO | --- Analysis for aksworg took 10.92508840560913s
Availability | SPARQL endpoint availability check for AlchemyAPI took 8.821487426757812e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.31751227378845215s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02256298065185547s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0011446475982666016s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.838539123535156e-05s
Believability | Calculation of trust value for AlchemyAPI took 1.1920928955078125e-05s
INFO | --- Analysis for alchemyapi took 3.024596691131592s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 393.71483421325684s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0007719993591308594s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.48108339309692383s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.02176213264465332s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.790855407714844e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 1.1920928955078125e-05s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 527.0085234642029s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 263.1914608478546s
Availability | VoID file availability check for aliada-scanbit-net took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.5251009464263916s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02156543731689453s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00012564659118652344s
Believability | Calculation of trust value for aliada-scanbit-net took 1.239776611328125e-05s
INFO | --- Analysis for aliada-scanbit-net took 1330.1922869682312s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 9.083747863769531e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.0009419918060302734s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.5513265132904053s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02286696434020996s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.147125244140625e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 1.239776611328125e-05s
INFO | --- Analysis for allen-brain-atlas took 16.191083669662476s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.8915419578552246s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006890296936035156s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 139.12442278862s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7121024131774902s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.6039316654205322s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.5141491889953613s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0236060619354s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.767355442047119s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8720464706420898s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.5846316814422607s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.5794737339019775s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.570624828338623s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5773026943206787s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 30.258185148239136s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5708765983581543s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.8410451412200928s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.4871156215667725s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5851218700408936s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6230552196502686s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.7202436923980713s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.794260501861572s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 9.179115295410156e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5482838153839111s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.56815505027771s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5797977447509766s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5455706119537354s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5610251426696777s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 0.5680220127105713s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 0.5649759769439697s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 51.03056025505066s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 4.524682283401489s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5739073753356934s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6517157554626465s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6144065856933594s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 34.46983790397644s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0939247608184814s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.707975149154663s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.632537841796875s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.08777904510498s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 9.050751447677612s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 31.41834545135498s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.405371904373169s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 10.947441101074219s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.9313182830810547s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8526012897491455s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.550386905670166s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 14048.483026742935s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 119.95191240310669s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02203965187072754s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.0001270771026611328s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 10.504125356674194s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.8358230590820312e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 15217.33983039856s
Availability | SPARQL endpoint availability check for Alojamientos took 4.267692565917969e-05s
Availability | VoID file availability check for Alojamientos took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Alojamientos took 156.14512085914612s
Reputation | Calculation of the PageRank for Alojamientos took 0.022694826126098633s
Interlinking | Calculation of Degree of Connection for Alojamientos took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0010900497436523438s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 4.57763671875e-05s
Believability | Calculation of trust value for Alojamientos took 1.3589859008789062e-05s
INFO | --- Analysis for alojamientos-zaragoza took 717.1136314868927s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.41219520568847656s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 179.71586918830872s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.021040916442871094s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.482269287109375e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.2874603271484375e-05s
INFO | --- Analysis for alpino-rdf took 243.18327450752258s
Availability | SPARQL endpoint availability check for AAT-atawil took 9.107589721679688e-05s
Availability | VoID file availability check for AAT-atawil took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for AAT-atawil took 60.1700177192688s
Reputation | Calculation of the PageRank for AAT-atawil took 0.021486282348632812s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.8623809814453125e-05s
Believability | Calculation of trust value for AAT-atawil took 1.239776611328125e-05s
INFO | --- Analysis for Altawil took 188.72171711921692s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 7.076091051101685s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 67.00120282173157s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.021222591400146484s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.5762786865234375e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.1920928955078125e-05s
INFO | --- Analysis for am-collections-online took 169.67166018486023s
Availability | SPARQL endpoint availability check for Amer Nejma took 9.417533874511719e-05s
Availability | VoID file availability check for Amer Nejma took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Amer Nejma took 48.983468770980835s
Reputation | Calculation of the PageRank for Amer Nejma took 0.023993730545043945s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0008878707885742188s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.24249267578125e-05s
Believability | Calculation of trust value for Amer Nejma took 1.239776611328125e-05s
INFO | --- Analysis for Amer_Nejma took 178.95106434822083s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.4309113025665283s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.021167993545532227s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.7670135498046875e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for amon took 121.75174403190613s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7138044834136963s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 179.96116662025452s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.022714853286743164s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0010569095611572266s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0001354217529296875s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.2159347534179688e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 578.6356732845306s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 8.726119995117188e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 22.624590396881104s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.021381378173828125s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.933906555175781e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 1.1920928955078125e-05s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 82.69990849494934s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 9.179115295410156e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.3139791488647461s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02247452735900879s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0010542869567871094s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.790855407714844e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.4781951904296875e-05s
INFO | --- Analysis for animal-diversity-web took 18.56369972229004s
Availability | SPARQL endpoint availability check for Anime Dataset took 8.654594421386719e-05s
Availability | VoID file availability check for Anime Dataset took 0.0004100799560546875s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.3328394889831543s
Reputation | Calculation of the PageRank for Anime Dataset took 0.02111363410949707s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Anime Dataset took 1.1444091796875e-05s
INFO | --- Analysis for Anime took 3.4385883808135986s
Availability | SPARQL endpoint availability check for ANNO took 8.7738037109375e-05s
Availability | VoID file availability check for ANNO took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for ANNO took 0.48151516914367676s
Reputation | Calculation of the PageRank for ANNO took 0.02132701873779297s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0008661746978759766s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.6716461181640625e-05s
Believability | Calculation of trust value for ANNO took 1.1444091796875e-05s
INFO | --- Analysis for anno took 7.85263466835022s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 0.00011086463928222656s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 1.1528174877166748s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.02126908302307129s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 9.72747802734375e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 7.62939453125e-06s
INFO | --- Analysis for AntiqueCarsCollection took 3.6941661834716797s
Availability | SPARQL endpoint availability check for apache took 8.940696716308594e-05s
Availability | VoID file availability check for apache took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for apache took 0.3030097484588623s
Reputation | Calculation of the PageRank for apache took 0.0232546329498291s
Interlinking | Calculation of Degree of Connection for apache took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for apache took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for apache took 5.412101745605469e-05s
Believability | Calculation of trust value for apache took 1.1205673217773438e-05s
INFO | --- Analysis for apache took 2.7649388313293457s
Availability | SPARQL endpoint availability check for Apertium RDF took 1.3040077686309814s
Availability | VoID file availability check for Apertium RDF took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.3093428611755371s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf took 16.514187812805176s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 0.288313627243042s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006983280181884766s
Extra | Recovery of all triples for Apertium RDF CA-IT took 264.80187582969666s
Performance | Total latancy measurement for Apertium RDF CA-IT took 1.3902256488800049s
Amount of data | Number of triples check for Apertium RDF CA-IT took 2.2893929481506348s
Interoperability | New terms check for Apertium RDF CA-IT took 3.035508155822754s
Versatility | Languages check for Apertium RDF CA-IT took 44.82068657875061s
Interpretability | Number of blank nodes check for Apertium RDF CA-IT took 1.2008471488952637s
Security | Check HTTPS for Apertium RDF CA-IT took 0.13376379013061523s
Interpretability | RDF structures check for Apertium RDF CA-IT took 0.29657912254333496s
Versatility | Serialization formats check for Apertium RDF CA-IT took 0.26184916496276855s
Availability | RDF dump link check for Apertium RDF CA-IT took 0.2729358673095703s
License | MR license check for Apertium RDF CA-IT took 0.28302550315856934s
License | HR license check for Apertium RDF CA-IT took 0.3638749122619629s
Amount of data | Number of property check for Apertium RDF CA-IT took 0.29099321365356445s
Understandability | Number of label check for Apertium RDF CA-IT took 0.33629608154296875s
Understandability | URI regex check for Apertium RDF CA-IT took 0.580723762512207s
Understandability | Vocabs check for Apertium RDF CA-IT took 0.26035046577453613s
Verifiability | Authors check for Apertium RDF CA-IT took 0.3274078369140625s
Verifiability | Publishers check for Apertium RDF CA-IT took 0.2817096710205078s
Performance | Throughput check for Apertium RDF CA-IT took 11.513916015625s
Amount of data | Check the number of entities for Apertium RDF CA-IT took 0.00013899803161621094s
Verifiability | Contribs. check for Apertium RDF CA-IT took 0.2981908321380615s
Interlinking | sameAs chians check for Apertium RDF CA-IT took 0.2671077251434326s
Interlinking | skos check for Apertium RDF CA-IT took 0.2879176139831543s
Interlinking | skos check for Apertium RDF CA-IT took 0.22437667846679688s
Timeliness | dataset update frequency check for Apertium RDF CA-IT took 0.2768385410308838s
Currency | Creation date check for Apertium RDF CA-IT took 0.28023576736450195s
Currency | Modification date check for Apertium RDF CA-IT took 0.2802391052246094s
Rep.Conc. | URIs length for Apertium RDF CA-IT took 86.11729764938354s
Interoperability | New vocabularies check for Apertium RDF CA-IT took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF CA-IT took 0.37343811988830566s
Accuracy | Check Functional Property for Apertium RDF CA-IT took 0.2826831340789795s
Accuracy | Check Inverse Functional Property for Apertium RDF CA-IT took 0.283402681350708s
Accuracy | Check Empty annotation labels for Apertium RDF CA-IT took 0.835928201675415s
Accuracy | Check White space in annotation for Apertium RDF CA-IT took 0.010327577590942383s
Accuracy | Check Datatype consistency for Apertium RDF CA-IT took 2.6761300563812256s
Consistency | Disjoint class check for Apertium RDF CA-IT took 0.28653907775878906s
Consistency | Check Misplaced properties for Apertium RDF CA-IT took 4.7084434032440186s
Consistency | Misplaced classes for Apertium RDF CA-IT took 8.716492414474487s
Consistency | Check Ontology hijacking for Apertium RDF CA-IT took 90.97716569900513s
Consistency | Check Invalid usage of undefined classes for Apertium RDF CA-IT took 1.5737237930297852s
Consistency | Check Invalid usage of undefined properties for Apertium RDF CA-IT took 5.794591665267944s
Conciseness | Check Extensional conciseness for Apertium RDF CA-IT took 3.108835220336914s
Conciseness | Check Intensional conciseness for Apertium RDF CA-IT took 0.3166072368621826s
Security | Sign check for Apertium RDF CA-IT took 0.28510141372680664s
Availability | Check URIs Dereferenciability for Apertium RDF CA-IT took 11.116338729858398s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.304309606552124s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.0207827091217041s
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.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF CA-IT took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 614.515282869339s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 0.2371842861175537s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006592273712158203s
Extra | Recovery of all triples for Apertium RDF EN-CA took 265.41101574897766s
Performance | Total latancy measurement for Apertium RDF EN-CA took 1.3129370212554932s
Amount of data | Number of triples check for Apertium RDF EN-CA took 2.226655960083008s
Interoperability | New terms check for Apertium RDF EN-CA took 2.920233726501465s
Versatility | Languages check for Apertium RDF EN-CA took 43.85602164268494s
Interpretability | Number of blank nodes check for Apertium RDF EN-CA took 1.2200500965118408s
Security | Check HTTPS for Apertium RDF EN-CA took 0.14501714706420898s
Interpretability | RDF structures check for Apertium RDF EN-CA took 0.33168673515319824s
Versatility | Serialization formats check for Apertium RDF EN-CA took 0.28425121307373047s
Availability | RDF dump link check for Apertium RDF EN-CA took 0.28376102447509766s
License | MR license check for Apertium RDF EN-CA took 0.27385973930358887s
License | HR license check for Apertium RDF EN-CA took 0.3615100383758545s
Amount of data | Number of property check for Apertium RDF EN-CA took 0.29598236083984375s
Understandability | Number of label check for Apertium RDF EN-CA took 0.31784987449645996s
Understandability | URI regex check for Apertium RDF EN-CA took 0.5424485206604004s
Understandability | Vocabs check for Apertium RDF EN-CA took 0.27501893043518066s
Verifiability | Authors check for Apertium RDF EN-CA took 0.2992980480194092s
Verifiability | Publishers check for Apertium RDF EN-CA took 0.290233850479126s
Performance | Throughput check for Apertium RDF EN-CA took 11.344178676605225s
Amount of data | Check the number of entities for Apertium RDF EN-CA took 8.940696716308594e-05s
Verifiability | Contribs. check for Apertium RDF EN-CA took 0.2983968257904053s
Interlinking | sameAs chians check for Apertium RDF EN-CA took 0.29123425483703613s
Interlinking | skos check for Apertium RDF EN-CA took 0.3180856704711914s
Interlinking | skos check for Apertium RDF EN-CA took 0.20619869232177734s
Timeliness | dataset update frequency check for Apertium RDF EN-CA took 0.26349878311157227s
Currency | Creation date check for Apertium RDF EN-CA took 0.3057396411895752s
Currency | Modification date check for Apertium RDF EN-CA took 0.3475668430328369s
Rep.Conc. | URIs length for Apertium RDF EN-CA took 91.04383945465088s
Interoperability | New vocabularies check for Apertium RDF EN-CA took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-CA took 0.29741835594177246s
Accuracy | Check Functional Property for Apertium RDF EN-CA took 0.2820413112640381s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-CA took 0.29205822944641113s
Accuracy | Check Empty annotation labels for Apertium RDF EN-CA took 0.8409078121185303s
Accuracy | Check White space in annotation for Apertium RDF EN-CA took 0.010177135467529297s
Accuracy | Check Datatype consistency for Apertium RDF EN-CA took 2.728062152862549s
Consistency | Disjoint class check for Apertium RDF EN-CA took 0.38357067108154297s
Consistency | Check Misplaced properties for Apertium RDF EN-CA took 4.632588863372803s
Consistency | Misplaced classes for Apertium RDF EN-CA took 8.796181440353394s
Consistency | Check Ontology hijacking for Apertium RDF EN-CA took 96.1055965423584s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-CA took 1.540346622467041s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-CA took 5.864626169204712s
Conciseness | Check Extensional conciseness for Apertium RDF EN-CA took 3.1763367652893066s
Conciseness | Check Intensional conciseness for Apertium RDF EN-CA took 0.3204324245452881s
Security | Sign check for Apertium RDF EN-CA took 0.2860438823699951s
Availability | Check URIs Dereferenciability for Apertium RDF EN-CA took 9.81823444366455s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.364194393157959s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.021097660064697266s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 638.8022568225861s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.22359180450439453s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.00034427642822265625s
Extra | Recovery of all triples for Apertium RDF EN-ES took 253.47734761238098s
Performance | Total latancy measurement for Apertium RDF EN-ES took 1.2478344440460205s
Amount of data | Number of triples check for Apertium RDF EN-ES took 2.1228697299957275s
Interoperability | New terms check for Apertium RDF EN-ES took 2.9162278175354004s
Versatility | Languages check for Apertium RDF EN-ES took 43.81760215759277s
Interpretability | Number of blank nodes check for Apertium RDF EN-ES took 1.1661505699157715s
Security | Check HTTPS for Apertium RDF EN-ES took 0.14461255073547363s
Interpretability | RDF structures check for Apertium RDF EN-ES took 0.26769089698791504s
Versatility | Serialization formats check for Apertium RDF EN-ES took 0.2706000804901123s
Availability | RDF dump link check for Apertium RDF EN-ES took 0.29126453399658203s
License | MR license check for Apertium RDF EN-ES took 0.29497504234313965s
License | HR license check for Apertium RDF EN-ES took 0.3851168155670166s
Amount of data | Number of property check for Apertium RDF EN-ES took 0.29403090476989746s
Understandability | Number of label check for Apertium RDF EN-ES took 0.305279016494751s
Understandability | URI regex check for Apertium RDF EN-ES took 0.5795586109161377s
Understandability | Vocabs check for Apertium RDF EN-ES took 0.2888317108154297s
Verifiability | Authors check for Apertium RDF EN-ES took 0.3314046859741211s
Verifiability | Publishers check for Apertium RDF EN-ES took 0.27625203132629395s
Performance | Throughput check for Apertium RDF EN-ES took 11.466018438339233s
Amount of data | Check the number of entities for Apertium RDF EN-ES took 9.202957153320312e-05s
Verifiability | Contribs. check for Apertium RDF EN-ES took 0.29882335662841797s
Interlinking | sameAs chians check for Apertium RDF EN-ES took 0.2830808162689209s
Interlinking | skos check for Apertium RDF EN-ES took 0.28603291511535645s
Interlinking | skos check for Apertium RDF EN-ES took 0.22576451301574707s
Timeliness | dataset update frequency check for Apertium RDF EN-ES took 0.26679229736328125s
Currency | Creation date check for Apertium RDF EN-ES took 0.2786731719970703s
Currency | Modification date check for Apertium RDF EN-ES took 0.29318976402282715s
Rep.Conc. | URIs length for Apertium RDF EN-ES took 90.56617736816406s
Interoperability | New vocabularies check for Apertium RDF EN-ES took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-ES took 0.3194844722747803s
Accuracy | Check Functional Property for Apertium RDF EN-ES took 0.2789328098297119s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-ES took 0.2708587646484375s
Accuracy | Check Empty annotation labels for Apertium RDF EN-ES took 0.8345339298248291s
Accuracy | Check White space in annotation for Apertium RDF EN-ES took 0.010336637496948242s
Accuracy | Check Datatype consistency for Apertium RDF EN-ES took 2.7423977851867676s
Consistency | Disjoint class check for Apertium RDF EN-ES took 0.27405309677124023s
Consistency | Check Misplaced properties for Apertium RDF EN-ES took 4.696772813796997s
Consistency | Misplaced classes for Apertium RDF EN-ES took 8.79091477394104s
Consistency | Check Ontology hijacking for Apertium RDF EN-ES took 86.43085432052612s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-ES took 1.568504810333252s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-ES took 5.655745506286621s
Conciseness | Check Extensional conciseness for Apertium RDF EN-ES took 3.2441232204437256s
Conciseness | Check Intensional conciseness for Apertium RDF EN-ES took 0.32286739349365234s
Security | Sign check for Apertium RDF EN-ES took 0.29140591621398926s
Availability | Check URIs Dereferenciability for Apertium RDF EN-ES took 11.502726554870605s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.3764011859893799s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02100849151611328s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-ES took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF EN-ES took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-en-es took 614.4376587867737s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 0.2312171459197998s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006589889526367188s
Extra | Recovery of all triples for Apertium RDF EN-GL took 264.3456711769104s
Performance | Total latancy measurement for Apertium RDF EN-GL took 1.2356414794921875s
Amount of data | Number of triples check for Apertium RDF EN-GL took 2.1825294494628906s
Interoperability | New terms check for Apertium RDF EN-GL took 2.973414182662964s
Versatility | Languages check for Apertium RDF EN-GL took 43.762043476104736s
Interpretability | Number of blank nodes check for Apertium RDF EN-GL took 1.219773769378662s
Security | Check HTTPS for Apertium RDF EN-GL took 0.13543009757995605s
Interpretability | RDF structures check for Apertium RDF EN-GL took 0.27846312522888184s
Versatility | Serialization formats check for Apertium RDF EN-GL took 0.2954399585723877s
Availability | RDF dump link check for Apertium RDF EN-GL took 0.2926015853881836s
License | MR license check for Apertium RDF EN-GL took 0.2992219924926758s
License | HR license check for Apertium RDF EN-GL took 0.4216156005859375s
Amount of data | Number of property check for Apertium RDF EN-GL took 0.28507351875305176s
Understandability | Number of label check for Apertium RDF EN-GL took 0.3498098850250244s
Understandability | URI regex check for Apertium RDF EN-GL took 0.5741715431213379s
Understandability | Vocabs check for Apertium RDF EN-GL took 0.2599945068359375s
Verifiability | Authors check for Apertium RDF EN-GL took 0.31262683868408203s
Verifiability | Publishers check for Apertium RDF EN-GL took 0.27076077461242676s
Performance | Throughput check for Apertium RDF EN-GL took 11.179834127426147s
Amount of data | Check the number of entities for Apertium RDF EN-GL took 0.00045752525329589844s
Verifiability | Contribs. check for Apertium RDF EN-GL took 0.27111172676086426s
Interlinking | sameAs chians check for Apertium RDF EN-GL took 0.2723419666290283s
Interlinking | skos check for Apertium RDF EN-GL took 0.2951188087463379s
Interlinking | skos check for Apertium RDF EN-GL took 0.21251726150512695s
Timeliness | dataset update frequency check for Apertium RDF EN-GL took 0.2932159900665283s
Currency | Creation date check for Apertium RDF EN-GL took 0.28383421897888184s
Currency | Modification date check for Apertium RDF EN-GL took 0.29469919204711914s
Rep.Conc. | URIs length for Apertium RDF EN-GL took 92.81251549720764s
Interoperability | New vocabularies check for Apertium RDF EN-GL took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-GL took 0.3164968490600586s
Accuracy | Check Functional Property for Apertium RDF EN-GL took 0.2883617877960205s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-GL took 0.28554320335388184s
Accuracy | Check Empty annotation labels for Apertium RDF EN-GL took 0.8460896015167236s
Accuracy | Check White space in annotation for Apertium RDF EN-GL took 0.010374069213867188s
Accuracy | Check Datatype consistency for Apertium RDF EN-GL took 2.7949366569519043s
Consistency | Disjoint class check for Apertium RDF EN-GL took 0.28322362899780273s
Consistency | Check Misplaced properties for Apertium RDF EN-GL took 4.680122137069702s
Consistency | Misplaced classes for Apertium RDF EN-GL took 8.784401655197144s
Consistency | Check Ontology hijacking for Apertium RDF EN-GL took 85.3571949005127s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-GL took 1.5646955966949463s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-GL took 5.792800188064575s
Conciseness | Check Extensional conciseness for Apertium RDF EN-GL took 3.2685351371765137s
Conciseness | Check Intensional conciseness for Apertium RDF EN-GL took 0.3086097240447998s
Security | Sign check for Apertium RDF EN-GL took 0.2746603488922119s
Availability | Check URIs Dereferenciability for Apertium RDF EN-GL took 11.135932683944702s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.9725914001464844s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.021991252899169922s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0009369850158691406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-GL took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 626.1139733791351s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 0.24155378341674805s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0004401206970214844s
Extra | Recovery of all triples for Apertium RDF EO-CA took 252.52120876312256s
Performance | Total latancy measurement for Apertium RDF EO-CA took 1.273308515548706s
Amount of data | Number of triples check for Apertium RDF EO-CA took 4.138158082962036s
Interoperability | New terms check for Apertium RDF EO-CA took 2.9322004318237305s
Versatility | Languages check for Apertium RDF EO-CA took 43.74984407424927s
Interpretability | Number of blank nodes check for Apertium RDF EO-CA took 1.2140755653381348s
Security | Check HTTPS for Apertium RDF EO-CA took 0.1224067211151123s
Interpretability | RDF structures check for Apertium RDF EO-CA took 0.2860255241394043s
Versatility | Serialization formats check for Apertium RDF EO-CA took 0.2892591953277588s
Availability | RDF dump link check for Apertium RDF EO-CA took 0.2752954959869385s
License | MR license check for Apertium RDF EO-CA took 0.28186631202697754s
License | HR license check for Apertium RDF EO-CA took 0.3666572570800781s
Amount of data | Number of property check for Apertium RDF EO-CA took 0.2626955509185791s
Understandability | Number of label check for Apertium RDF EO-CA took 0.30759668350219727s
Understandability | URI regex check for Apertium RDF EO-CA took 0.5299220085144043s
Understandability | Vocabs check for Apertium RDF EO-CA took 0.2921299934387207s
Verifiability | Authors check for Apertium RDF EO-CA took 0.31260204315185547s
Verifiability | Publishers check for Apertium RDF EO-CA took 0.2933938503265381s
Performance | Throughput check for Apertium RDF EO-CA took 11.290164709091187s
Amount of data | Check the number of entities for Apertium RDF EO-CA took 9.393692016601562e-05s
Verifiability | Contribs. check for Apertium RDF EO-CA took 0.2862813472747803s
Interlinking | sameAs chians check for Apertium RDF EO-CA took 0.2950022220611572s
Interlinking | skos check for Apertium RDF EO-CA took 0.278749942779541s
Interlinking | skos check for Apertium RDF EO-CA took 0.22478556632995605s
Timeliness | dataset update frequency check for Apertium RDF EO-CA took 0.29328155517578125s
Currency | Creation date check for Apertium RDF EO-CA took 0.30357980728149414s
Currency | Modification date check for Apertium RDF EO-CA took 0.28755760192871094s
Rep.Conc. | URIs length for Apertium RDF EO-CA took 89.93292570114136s
Interoperability | New vocabularies check for Apertium RDF EO-CA took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-CA took 0.3143651485443115s
Accuracy | Check Functional Property for Apertium RDF EO-CA took 0.2911050319671631s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-CA took 0.2889895439147949s
Accuracy | Check Empty annotation labels for Apertium RDF EO-CA took 0.849083662033081s
Accuracy | Check White space in annotation for Apertium RDF EO-CA took 0.010293006896972656s
Accuracy | Check Datatype consistency for Apertium RDF EO-CA took 2.7827701568603516s
Consistency | Disjoint class check for Apertium RDF EO-CA took 0.2708606719970703s
Consistency | Check Misplaced properties for Apertium RDF EO-CA took 4.6358256340026855s
Consistency | Misplaced classes for Apertium RDF EO-CA took 8.784595251083374s
Consistency | Check Ontology hijacking for Apertium RDF EO-CA took 96.82092809677124s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-CA took 1.5532715320587158s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-CA took 5.8237998485565186s
Conciseness | Check Extensional conciseness for Apertium RDF EO-CA took 3.28621506690979s
Conciseness | Check Intensional conciseness for Apertium RDF EO-CA took 0.31270575523376465s
Security | Sign check for Apertium RDF EO-CA took 0.27901506423950195s
Availability | Check URIs Dereferenciability for Apertium RDF EO-CA took 9.65177321434021s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.3758254051208496s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.021284818649291992s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-CA took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 626.1391546726227s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 0.22295165061950684s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.00066375732421875s
Extra | Recovery of all triples for Apertium RDF EO-EN took 275.52513217926025s
Performance | Total latancy measurement for Apertium RDF EO-EN took 1.250171184539795s
Amount of data | Number of triples check for Apertium RDF EO-EN took 2.106492519378662s
Interoperability | New terms check for Apertium RDF EO-EN took 2.9407153129577637s
Versatility | Languages check for Apertium RDF EO-EN took 43.611403465270996s
Interpretability | Number of blank nodes check for Apertium RDF EO-EN took 1.2425332069396973s
Security | Check HTTPS for Apertium RDF EO-EN took 0.13441705703735352s
Interpretability | RDF structures check for Apertium RDF EO-EN took 0.2794663906097412s
Versatility | Serialization formats check for Apertium RDF EO-EN took 0.28620076179504395s
Availability | RDF dump link check for Apertium RDF EO-EN took 0.2862520217895508s
License | MR license check for Apertium RDF EO-EN took 0.2756984233856201s
License | HR license check for Apertium RDF EO-EN took 0.37998437881469727s
Amount of data | Number of property check for Apertium RDF EO-EN took 0.279616117477417s
Understandability | Number of label check for Apertium RDF EO-EN took 0.296583890914917s
Understandability | URI regex check for Apertium RDF EO-EN took 0.5410416126251221s
Understandability | Vocabs check for Apertium RDF EO-EN took 0.2734966278076172s
Verifiability | Authors check for Apertium RDF EO-EN took 0.31688666343688965s
Verifiability | Publishers check for Apertium RDF EO-EN took 0.2698020935058594s
Performance | Throughput check for Apertium RDF EO-EN took 11.02581238746643s
Amount of data | Check the number of entities for Apertium RDF EO-EN took 9.34600830078125e-05s
Verifiability | Contribs. check for Apertium RDF EO-EN took 0.3077201843261719s
Interlinking | sameAs chians check for Apertium RDF EO-EN took 0.27544093132019043s
Interlinking | skos check for Apertium RDF EO-EN took 0.2601609230041504s
Interlinking | skos check for Apertium RDF EO-EN took 0.2285938262939453s
Timeliness | dataset update frequency check for Apertium RDF EO-EN took 0.28316307067871094s
Currency | Creation date check for Apertium RDF EO-EN took 0.28750085830688477s
Currency | Modification date check for Apertium RDF EO-EN took 0.28544163703918457s
Rep.Conc. | URIs length for Apertium RDF EO-EN took 90.4847457408905s
Interoperability | New vocabularies check for Apertium RDF EO-EN took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-EN took 0.2904510498046875s
Accuracy | Check Functional Property for Apertium RDF EO-EN took 0.2849249839782715s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-EN took 0.28464436531066895s
Accuracy | Check Empty annotation labels for Apertium RDF EO-EN took 0.8549151420593262s
Accuracy | Check White space in annotation for Apertium RDF EO-EN took 0.010220527648925781s
Accuracy | Check Datatype consistency for Apertium RDF EO-EN took 2.7491540908813477s
Consistency | Disjoint class check for Apertium RDF EO-EN took 0.2900364398956299s
Consistency | Check Misplaced properties for Apertium RDF EO-EN took 4.570556163787842s
Consistency | Misplaced classes for Apertium RDF EO-EN took 8.77258825302124s
Consistency | Check Ontology hijacking for Apertium RDF EO-EN took 85.757155418396s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-EN took 1.5287418365478516s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-EN took 5.8909618854522705s
Conciseness | Check Extensional conciseness for Apertium RDF EO-EN took 3.273205280303955s
Conciseness | Check Intensional conciseness for Apertium RDF EO-EN took 0.3339226245880127s
Security | Sign check for Apertium RDF EO-EN took 0.28200578689575195s
Availability | Check URIs Dereferenciability for Apertium RDF EO-EN took 11.709473133087158s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.3579883575439453s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.021004676818847656s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-EN took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 631.6410975456238s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 0.22260808944702148s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006730556488037109s
Extra | Recovery of all triples for Apertium RDF EO-ES took 279.22237253189087s
Performance | Total latancy measurement for Apertium RDF EO-ES took 1.2565081119537354s
Amount of data | Number of triples check for Apertium RDF EO-ES took 2.0702242851257324s
Interoperability | New terms check for Apertium RDF EO-ES took 3.1337878704071045s
Versatility | Languages check for Apertium RDF EO-ES took 43.8629105091095s
Interpretability | Number of blank nodes check for Apertium RDF EO-ES took 1.313063144683838s
Security | Check HTTPS for Apertium RDF EO-ES took 0.13541054725646973s
Interpretability | RDF structures check for Apertium RDF EO-ES took 0.2802860736846924s
Versatility | Serialization formats check for Apertium RDF EO-ES took 0.2646634578704834s
Availability | RDF dump link check for Apertium RDF EO-ES took 0.2846708297729492s
License | MR license check for Apertium RDF EO-ES took 0.29199790954589844s
License | HR license check for Apertium RDF EO-ES took 0.36557960510253906s
Amount of data | Number of property check for Apertium RDF EO-ES took 0.28160619735717773s
Understandability | Number of label check for Apertium RDF EO-ES took 0.31300878524780273s
Understandability | URI regex check for Apertium RDF EO-ES took 0.5730190277099609s
Understandability | Vocabs check for Apertium RDF EO-ES took 0.2739450931549072s
Verifiability | Authors check for Apertium RDF EO-ES took 0.3384828567504883s
Verifiability | Publishers check for Apertium RDF EO-ES took 0.28437042236328125s
Performance | Throughput check for Apertium RDF EO-ES took 11.229567289352417s
Amount of data | Check the number of entities for Apertium RDF EO-ES took 8.916854858398438e-05s
Verifiability | Contribs. check for Apertium RDF EO-ES took 0.3013582229614258s
Interlinking | sameAs chians check for Apertium RDF EO-ES took 0.27280235290527344s
Interlinking | skos check for Apertium RDF EO-ES took 0.2736520767211914s
Interlinking | skos check for Apertium RDF EO-ES took 0.23200607299804688s
Timeliness | dataset update frequency check for Apertium RDF EO-ES took 0.286243200302124s
Currency | Creation date check for Apertium RDF EO-ES took 0.2936573028564453s
Currency | Modification date check for Apertium RDF EO-ES took 0.3022141456604004s
Rep.Conc. | URIs length for Apertium RDF EO-ES took 87.90024065971375s
Interoperability | New vocabularies check for Apertium RDF EO-ES took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-ES took 0.31291675567626953s
Accuracy | Check Functional Property for Apertium RDF EO-ES took 0.3052244186401367s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-ES took 0.285524845123291s
Accuracy | Check Empty annotation labels for Apertium RDF EO-ES took 0.8466901779174805s
Accuracy | Check White space in annotation for Apertium RDF EO-ES took 0.010290861129760742s
Accuracy | Check Datatype consistency for Apertium RDF EO-ES took 2.7753632068634033s
Consistency | Disjoint class check for Apertium RDF EO-ES took 0.2879006862640381s
Consistency | Check Misplaced properties for Apertium RDF EO-ES took 4.664289236068726s
Consistency | Misplaced classes for Apertium RDF EO-ES took 8.766171216964722s
Consistency | Check Ontology hijacking for Apertium RDF EO-ES took 95.89435720443726s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-ES took 1.5893969535827637s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-ES took 5.801182746887207s
Conciseness | Check Extensional conciseness for Apertium RDF EO-ES took 3.2743091583251953s
Conciseness | Check Intensional conciseness for Apertium RDF EO-ES took 0.3216876983642578s
Security | Sign check for Apertium RDF EO-ES took 0.2719252109527588s
Availability | Check URIs Dereferenciability for Apertium RDF EO-ES took 17.549219131469727s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.7531394958496094s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0008144378662109375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-ES took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 652.7448062896729s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 0.21620607376098633s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0004913806915283203s
Extra | Recovery of all triples for Apertium RDF EO-FR took 266.8282678127289s
Performance | Total latancy measurement for Apertium RDF EO-FR took 1.2617883682250977s
Amount of data | Number of triples check for Apertium RDF EO-FR took 2.165142297744751s
Interoperability | New terms check for Apertium RDF EO-FR took 2.940154552459717s
Versatility | Languages check for Apertium RDF EO-FR took 43.7001736164093s
Interpretability | Number of blank nodes check for Apertium RDF EO-FR took 2.8012828826904297s
Security | Check HTTPS for Apertium RDF EO-FR took 0.13530611991882324s
Interpretability | RDF structures check for Apertium RDF EO-FR took 0.28715991973876953s
Versatility | Serialization formats check for Apertium RDF EO-FR took 0.2833833694458008s
Availability | RDF dump link check for Apertium RDF EO-FR took 0.2912313938140869s
License | MR license check for Apertium RDF EO-FR took 0.5362730026245117s
License | HR license check for Apertium RDF EO-FR took 0.3876497745513916s
Amount of data | Number of property check for Apertium RDF EO-FR took 0.5528106689453125s
Understandability | Number of label check for Apertium RDF EO-FR took 0.31314754486083984s
Understandability | URI regex check for Apertium RDF EO-FR took 0.5811793804168701s
Understandability | Vocabs check for Apertium RDF EO-FR took 0.26224589347839355s
Verifiability | Authors check for Apertium RDF EO-FR took 0.32152748107910156s
Verifiability | Publishers check for Apertium RDF EO-FR took 0.2835350036621094s
Performance | Throughput check for Apertium RDF EO-FR took 11.186106443405151s
Amount of data | Check the number of entities for Apertium RDF EO-FR took 8.726119995117188e-05s
Verifiability | Contribs. check for Apertium RDF EO-FR took 0.29089784622192383s
Interlinking | sameAs chians check for Apertium RDF EO-FR took 0.36441493034362793s
Interlinking | skos check for Apertium RDF EO-FR took 0.29668736457824707s
Interlinking | skos check for Apertium RDF EO-FR took 0.22651433944702148s
Timeliness | dataset update frequency check for Apertium RDF EO-FR took 0.26435160636901855s
Currency | Creation date check for Apertium RDF EO-FR took 0.2729325294494629s
Currency | Modification date check for Apertium RDF EO-FR took 0.2951834201812744s
Rep.Conc. | URIs length for Apertium RDF EO-FR took 90.38387393951416s
Interoperability | New vocabularies check for Apertium RDF EO-FR took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-FR took 0.30356431007385254s
Accuracy | Check Functional Property for Apertium RDF EO-FR took 0.27552366256713867s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-FR took 0.2827489376068115s
Accuracy | Check Empty annotation labels for Apertium RDF EO-FR took 0.8135249614715576s
Accuracy | Check White space in annotation for Apertium RDF EO-FR took 0.010282754898071289s
Accuracy | Check Datatype consistency for Apertium RDF EO-FR took 2.7647299766540527s
Consistency | Disjoint class check for Apertium RDF EO-FR took 0.2784585952758789s
Consistency | Check Misplaced properties for Apertium RDF EO-FR took 4.5859880447387695s
Consistency | Misplaced classes for Apertium RDF EO-FR took 8.782721042633057s
Consistency | Check Ontology hijacking for Apertium RDF EO-FR took 85.67370057106018s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-FR took 1.5489983558654785s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-FR took 6.025723457336426s
Conciseness | Check Extensional conciseness for Apertium RDF EO-FR took 3.418116331100464s
Conciseness | Check Intensional conciseness for Apertium RDF EO-FR took 0.3181877136230469s
Security | Sign check for Apertium RDF EO-FR took 0.28647780418395996s
Availability | Check URIs Dereferenciability for Apertium RDF EO-FR took 15.00995922088623s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 3.09128999710083s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-FR took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 658.1141588687897s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 0.2118692398071289s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006618499755859375s
Extra | Recovery of all triples for Apertium RDF ES-AN took 264.6955153942108s
Performance | Total latancy measurement for Apertium RDF ES-AN took 1.2830603122711182s
Amount of data | Number of triples check for Apertium RDF ES-AN took 2.1650197505950928s
Interoperability | New terms check for Apertium RDF ES-AN took 2.908139944076538s
Versatility | Languages check for Apertium RDF ES-AN took 43.66167068481445s
Interpretability | Number of blank nodes check for Apertium RDF ES-AN took 1.0571506023406982s
Security | Check HTTPS for Apertium RDF ES-AN took 0.13457107543945312s
Interpretability | RDF structures check for Apertium RDF ES-AN took 0.2829413414001465s
Versatility | Serialization formats check for Apertium RDF ES-AN took 0.26558995246887207s
Availability | RDF dump link check for Apertium RDF ES-AN took 0.2807435989379883s
License | MR license check for Apertium RDF ES-AN took 0.2880065441131592s
License | HR license check for Apertium RDF ES-AN took 0.3616914749145508s
Amount of data | Number of property check for Apertium RDF ES-AN took 0.2831740379333496s
Understandability | Number of label check for Apertium RDF ES-AN took 0.3367280960083008s
Understandability | URI regex check for Apertium RDF ES-AN took 0.581660270690918s
Understandability | Vocabs check for Apertium RDF ES-AN took 0.2635965347290039s
Verifiability | Authors check for Apertium RDF ES-AN took 0.30872082710266113s
Verifiability | Publishers check for Apertium RDF ES-AN took 0.2872025966644287s
Performance | Throughput check for Apertium RDF ES-AN took 15.86752963066101s
Amount of data | Check the number of entities for Apertium RDF ES-AN took 6.580352783203125e-05s
Verifiability | Contribs. check for Apertium RDF ES-AN took 0.2634134292602539s
Interlinking | sameAs chians check for Apertium RDF ES-AN took 0.290360689163208s
Interlinking | skos check for Apertium RDF ES-AN took 0.28440356254577637s
Interlinking | skos check for Apertium RDF ES-AN took 0.24675869941711426s
Timeliness | dataset update frequency check for Apertium RDF ES-AN took 0.2998998165130615s
Currency | Creation date check for Apertium RDF ES-AN took 0.28386878967285156s
Currency | Modification date check for Apertium RDF ES-AN took 0.28002166748046875s
Rep.Conc. | URIs length for Apertium RDF ES-AN took 91.1562111377716s
Interoperability | New vocabularies check for Apertium RDF ES-AN took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AN took 0.30211806297302246s
Accuracy | Check Functional Property for Apertium RDF ES-AN took 0.2887077331542969s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AN took 0.2959749698638916s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AN took 0.861358642578125s
Accuracy | Check White space in annotation for Apertium RDF ES-AN took 0.011893510818481445s
Accuracy | Check Datatype consistency for Apertium RDF ES-AN took 2.7614364624023438s
Consistency | Disjoint class check for Apertium RDF ES-AN took 0.29538917541503906s
Consistency | Check Misplaced properties for Apertium RDF ES-AN took 4.650439739227295s
Consistency | Misplaced classes for Apertium RDF ES-AN took 8.844039916992188s
Consistency | Check Ontology hijacking for Apertium RDF ES-AN took 90.96606254577637s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AN took 1.568256139755249s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AN took 5.836849212646484s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AN took 3.255275249481201s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AN took 2.5669405460357666s
Security | Sign check for Apertium RDF ES-AN took 0.27225446701049805s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AN took 15.359121322631836s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.3531026840209961s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.021416664123535156s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AN took 2.384185791015625e-06s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-es-an took 663.858558177948s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 0.2244272232055664s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006947517395019531s
Extra | Recovery of all triples for Apertium RDF ES-AST took 263.51367115974426s
Performance | Total latancy measurement for Apertium RDF ES-AST took 1.2573840618133545s
Amount of data | Number of triples check for Apertium RDF ES-AST took 2.1647400856018066s
Interoperability | New terms check for Apertium RDF ES-AST took 2.956055164337158s
Versatility | Languages check for Apertium RDF ES-AST took 43.76542568206787s
Interpretability | Number of blank nodes check for Apertium RDF ES-AST took 1.1994457244873047s
Security | Check HTTPS for Apertium RDF ES-AST took 0.13577032089233398s
Interpretability | RDF structures check for Apertium RDF ES-AST took 0.2970895767211914s
Versatility | Serialization formats check for Apertium RDF ES-AST took 0.2895393371582031s
Availability | RDF dump link check for Apertium RDF ES-AST took 0.2861137390136719s
License | MR license check for Apertium RDF ES-AST took 0.2795741558074951s
License | HR license check for Apertium RDF ES-AST took 0.3821284770965576s
Amount of data | Number of property check for Apertium RDF ES-AST took 0.3043935298919678s
Understandability | Number of label check for Apertium RDF ES-AST took 0.3035144805908203s
Understandability | URI regex check for Apertium RDF ES-AST took 0.5574445724487305s
Understandability | Vocabs check for Apertium RDF ES-AST took 0.28444862365722656s
Verifiability | Authors check for Apertium RDF ES-AST took 0.3189816474914551s
Verifiability | Publishers check for Apertium RDF ES-AST took 0.2848517894744873s
Performance | Throughput check for Apertium RDF ES-AST took 11.096327543258667s
Amount of data | Check the number of entities for Apertium RDF ES-AST took 0.0001544952392578125s
Verifiability | Contribs. check for Apertium RDF ES-AST took 0.27790331840515137s
Interlinking | sameAs chians check for Apertium RDF ES-AST took 0.26204729080200195s
Interlinking | skos check for Apertium RDF ES-AST took 0.2776768207550049s
Interlinking | skos check for Apertium RDF ES-AST took 0.2281341552734375s
Timeliness | dataset update frequency check for Apertium RDF ES-AST took 0.2790255546569824s
Currency | Creation date check for Apertium RDF ES-AST took 0.2778167724609375s
Currency | Modification date check for Apertium RDF ES-AST took 0.28807711601257324s
Rep.Conc. | URIs length for Apertium RDF ES-AST took 94.13720393180847s
Interoperability | New vocabularies check for Apertium RDF ES-AST took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AST took 0.30794239044189453s
Accuracy | Check Functional Property for Apertium RDF ES-AST took 0.2783396244049072s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AST took 0.27092909812927246s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AST took 0.8061428070068359s
Accuracy | Check White space in annotation for Apertium RDF ES-AST took 0.010248899459838867s
Accuracy | Check Datatype consistency for Apertium RDF ES-AST took 2.779751777648926s
Consistency | Disjoint class check for Apertium RDF ES-AST took 0.2859046459197998s
Consistency | Check Misplaced properties for Apertium RDF ES-AST took 4.7713942527771s
Consistency | Misplaced classes for Apertium RDF ES-AST took 8.861182451248169s
Consistency | Check Ontology hijacking for Apertium RDF ES-AST took 90.53336024284363s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AST took 1.6590347290039062s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AST took 6.073197841644287s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AST took 3.30013108253479s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AST took 0.33967041969299316s
Security | Sign check for Apertium RDF ES-AST took 0.28171753883361816s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AST took 21.394139289855957s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 1.9427192211151123s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AST took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 667.8115775585175s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 0.22296690940856934s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0009000301361083984s
Extra | Recovery of all triples for Apertium RDF ES-CA took 275.9917345046997s
Performance | Total latancy measurement for Apertium RDF ES-CA took 1.2541182041168213s
Amount of data | Number of triples check for Apertium RDF ES-CA took 2.2470226287841797s
Interoperability | New terms check for Apertium RDF ES-CA took 2.9328601360321045s
Versatility | Languages check for Apertium RDF ES-CA took 43.52291250228882s
Interpretability | Number of blank nodes check for Apertium RDF ES-CA took 1.1505014896392822s
Security | Check HTTPS for Apertium RDF ES-CA took 0.13315510749816895s
Interpretability | RDF structures check for Apertium RDF ES-CA took 0.26743531227111816s
Versatility | Serialization formats check for Apertium RDF ES-CA took 0.28477931022644043s
Availability | RDF dump link check for Apertium RDF ES-CA took 0.269695520401001s
License | MR license check for Apertium RDF ES-CA took 0.2856943607330322s
License | HR license check for Apertium RDF ES-CA took 0.3831348419189453s
Amount of data | Number of property check for Apertium RDF ES-CA took 0.2949075698852539s
Understandability | Number of label check for Apertium RDF ES-CA took 0.3020169734954834s
Understandability | URI regex check for Apertium RDF ES-CA took 0.5425593852996826s
Understandability | Vocabs check for Apertium RDF ES-CA took 0.2835252285003662s
Verifiability | Authors check for Apertium RDF ES-CA took 0.3131532669067383s
Verifiability | Publishers check for Apertium RDF ES-CA took 0.27600693702697754s
Performance | Throughput check for Apertium RDF ES-CA took 11.241803169250488s
Amount of data | Check the number of entities for Apertium RDF ES-CA took 0.0006632804870605469s
Verifiability | Contribs. check for Apertium RDF ES-CA took 0.2578725814819336s
Interlinking | sameAs chians check for Apertium RDF ES-CA took 0.26906514167785645s
Interlinking | skos check for Apertium RDF ES-CA took 0.2661116123199463s
Interlinking | skos check for Apertium RDF ES-CA took 0.23197221755981445s
Timeliness | dataset update frequency check for Apertium RDF ES-CA took 0.3602626323699951s
Currency | Creation date check for Apertium RDF ES-CA took 0.27028322219848633s
Currency | Modification date check for Apertium RDF ES-CA took 0.26520395278930664s
Rep.Conc. | URIs length for Apertium RDF ES-CA took 90.23994493484497s
Interoperability | New vocabularies check for Apertium RDF ES-CA took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-CA took 0.3190767765045166s
Accuracy | Check Functional Property for Apertium RDF ES-CA took 0.2613639831542969s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-CA took 0.27104949951171875s
Accuracy | Check Empty annotation labels for Apertium RDF ES-CA took 0.8483705520629883s
Accuracy | Check White space in annotation for Apertium RDF ES-CA took 0.010179281234741211s
Accuracy | Check Datatype consistency for Apertium RDF ES-CA took 2.7985587120056152s
Consistency | Disjoint class check for Apertium RDF ES-CA took 0.28403496742248535s
Consistency | Check Misplaced properties for Apertium RDF ES-CA took 4.710423707962036s
Consistency | Misplaced classes for Apertium RDF ES-CA took 8.722251892089844s
Consistency | Check Ontology hijacking for Apertium RDF ES-CA took 90.83898305892944s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-CA took 1.5311496257781982s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-CA took 6.014286994934082s
Conciseness | Check Extensional conciseness for Apertium RDF ES-CA took 3.273693084716797s
Conciseness | Check Intensional conciseness for Apertium RDF ES-CA took 0.3211405277252197s
Security | Sign check for Apertium RDF ES-CA took 0.2964024543762207s
Availability | Check URIs Dereferenciability for Apertium RDF ES-CA took 9.803241491317749s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 2.7950751781463623s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020897626876831055s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.410743713378906e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF ES-CA took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 675.5783424377441s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 0.23529291152954102s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006439685821533203s
Extra | Recovery of all triples for Apertium RDF ES-GL took 277.4046115875244s
Performance | Total latancy measurement for Apertium RDF ES-GL took 1.346560001373291s
Amount of data | Number of triples check for Apertium RDF ES-GL took 2.132819890975952s
Interoperability | New terms check for Apertium RDF ES-GL took 3.135369300842285s
Versatility | Languages check for Apertium RDF ES-GL took 44.11268973350525s
Interpretability | Number of blank nodes check for Apertium RDF ES-GL took 1.0573716163635254s
Security | Check HTTPS for Apertium RDF ES-GL took 0.13461565971374512s
Interpretability | RDF structures check for Apertium RDF ES-GL took 0.2660062313079834s
Versatility | Serialization formats check for Apertium RDF ES-GL took 0.2864725589752197s
Availability | RDF dump link check for Apertium RDF ES-GL took 0.2950937747955322s
License | MR license check for Apertium RDF ES-GL took 0.28021812438964844s
License | HR license check for Apertium RDF ES-GL took 0.35441112518310547s
Amount of data | Number of property check for Apertium RDF ES-GL took 0.30176520347595215s
Understandability | Number of label check for Apertium RDF ES-GL took 0.3647282123565674s
Understandability | URI regex check for Apertium RDF ES-GL took 0.5750792026519775s
Understandability | Vocabs check for Apertium RDF ES-GL took 0.278933048248291s
Verifiability | Authors check for Apertium RDF ES-GL took 0.3217036724090576s
Verifiability | Publishers check for Apertium RDF ES-GL took 0.2648320198059082s
Performance | Throughput check for Apertium RDF ES-GL took 11.37012791633606s
Amount of data | Check the number of entities for Apertium RDF ES-GL took 4.124641418457031e-05s
Verifiability | Contribs. check for Apertium RDF ES-GL took 0.29596996307373047s
Interlinking | sameAs chians check for Apertium RDF ES-GL took 0.29018735885620117s
Interlinking | skos check for Apertium RDF ES-GL took 0.2615938186645508s
Interlinking | skos check for Apertium RDF ES-GL took 0.2306215763092041s
Timeliness | dataset update frequency check for Apertium RDF ES-GL took 0.28262948989868164s
Currency | Creation date check for Apertium RDF ES-GL took 0.26924633979797363s
Currency | Modification date check for Apertium RDF ES-GL took 0.2868375778198242s
Rep.Conc. | URIs length for Apertium RDF ES-GL took 86.14406514167786s
Interoperability | New vocabularies check for Apertium RDF ES-GL took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-GL took 0.3242044448852539s
Accuracy | Check Functional Property for Apertium RDF ES-GL took 0.28063178062438965s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-GL took 0.2665250301361084s
Accuracy | Check Empty annotation labels for Apertium RDF ES-GL took 0.7593271732330322s
Accuracy | Check White space in annotation for Apertium RDF ES-GL took 0.010567188262939453s
Accuracy | Check Datatype consistency for Apertium RDF ES-GL took 2.72346568107605s
Consistency | Disjoint class check for Apertium RDF ES-GL took 0.2824976444244385s
Consistency | Check Misplaced properties for Apertium RDF ES-GL took 4.745046138763428s
Consistency | Misplaced classes for Apertium RDF ES-GL took 8.690093994140625s
Consistency | Check Ontology hijacking for Apertium RDF ES-GL took 85.1946804523468s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-GL took 1.5269222259521484s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-GL took 5.752993822097778s
Conciseness | Check Extensional conciseness for Apertium RDF ES-GL took 3.2943966388702393s
Conciseness | Check Intensional conciseness for Apertium RDF ES-GL took 0.3040895462036133s
Security | Sign check for Apertium RDF ES-GL took 0.2801225185394287s
Availability | Check URIs Dereferenciability for Apertium RDF ES-GL took 10.39554476737976s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.4155404567718506s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.021159887313842773s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-GL took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-GL took 2.0265579223632812e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 905.0919370651245s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 0.2281038761138916s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005605220794677734s
Extra | Recovery of all triples for Apertium RDF ES-PT took 275.8253653049469s
Performance | Total latancy measurement for Apertium RDF ES-PT took 1.2293028831481934s
Amount of data | Number of triples check for Apertium RDF ES-PT took 2.075092315673828s
Interoperability | New terms check for Apertium RDF ES-PT took 3.0911476612091064s
Versatility | Languages check for Apertium RDF ES-PT took 45.708383083343506s
Interpretability | Number of blank nodes check for Apertium RDF ES-PT took 1.1667232513427734s
Security | Check HTTPS for Apertium RDF ES-PT took 0.13557028770446777s
Interpretability | RDF structures check for Apertium RDF ES-PT took 0.3612058162689209s
Versatility | Serialization formats check for Apertium RDF ES-PT took 0.36685895919799805s
Availability | RDF dump link check for Apertium RDF ES-PT took 0.38007402420043945s
License | MR license check for Apertium RDF ES-PT took 0.5717947483062744s
License | HR license check for Apertium RDF ES-PT took 0.47174072265625s
Amount of data | Number of property check for Apertium RDF ES-PT took 0.38980531692504883s
Understandability | Number of label check for Apertium RDF ES-PT took 0.4224281311035156s
Understandability | URI regex check for Apertium RDF ES-PT took 0.7195127010345459s
Understandability | Vocabs check for Apertium RDF ES-PT took 0.374981164932251s
Verifiability | Authors check for Apertium RDF ES-PT took 0.4264054298400879s
Verifiability | Publishers check for Apertium RDF ES-PT took 0.3753035068511963s
Performance | Throughput check for Apertium RDF ES-PT took 11.256834745407104s
Amount of data | Check the number of entities for Apertium RDF ES-PT took 0.0003783702850341797s
Verifiability | Contribs. check for Apertium RDF ES-PT took 0.39805173873901367s
Interlinking | sameAs chians check for Apertium RDF ES-PT took 0.37622880935668945s
Interlinking | skos check for Apertium RDF ES-PT took 0.38747525215148926s
Interlinking | skos check for Apertium RDF ES-PT took 0.24516820907592773s
Timeliness | dataset update frequency check for Apertium RDF ES-PT took 0.3698453903198242s
Currency | Creation date check for Apertium RDF ES-PT took 0.3788278102874756s
Currency | Modification date check for Apertium RDF ES-PT took 0.3653442859649658s
Rep.Conc. | URIs length for Apertium RDF ES-PT took 86.84368133544922s
Interoperability | New vocabularies check for Apertium RDF ES-PT took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-PT took 0.293032169342041s
Accuracy | Check Functional Property for Apertium RDF ES-PT took 0.2783386707305908s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-PT took 0.28576111793518066s
Accuracy | Check Empty annotation labels for Apertium RDF ES-PT took 0.8468570709228516s
Accuracy | Check White space in annotation for Apertium RDF ES-PT took 0.010444402694702148s
Accuracy | Check Datatype consistency for Apertium RDF ES-PT took 2.739720582962036s
Consistency | Disjoint class check for Apertium RDF ES-PT took 0.2682321071624756s
Consistency | Check Misplaced properties for Apertium RDF ES-PT took 4.66102147102356s
Consistency | Misplaced classes for Apertium RDF ES-PT took 8.954894781112671s
Consistency | Check Ontology hijacking for Apertium RDF ES-PT took 90.58008241653442s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-PT took 1.5245308876037598s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-PT took 5.868906736373901s
Conciseness | Check Extensional conciseness for Apertium RDF ES-PT took 3.2858691215515137s
Conciseness | Check Intensional conciseness for Apertium RDF ES-PT took 0.36637401580810547s
Security | Sign check for Apertium RDF ES-PT took 0.27561140060424805s
Availability | Check URIs Dereferenciability for Apertium RDF ES-PT took 26.192657232284546s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.34901928901672363s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-PT took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 949.0517311096191s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 0.2247457504272461s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006041526794433594s
Extra | Recovery of all triples for Apertium RDF ES-RO took 279.27057218551636s
Performance | Total latancy measurement for Apertium RDF ES-RO took 2.9262828826904297s
Amount of data | Number of triples check for Apertium RDF ES-RO took 2.2158353328704834s
Interoperability | New terms check for Apertium RDF ES-RO took 2.938967227935791s
Versatility | Languages check for Apertium RDF ES-RO took 44.39748001098633s
Interpretability | Number of blank nodes check for Apertium RDF ES-RO took 1.1468467712402344s
Security | Check HTTPS for Apertium RDF ES-RO took 0.1352403163909912s
Interpretability | RDF structures check for Apertium RDF ES-RO took 0.2859532833099365s
Versatility | Serialization formats check for Apertium RDF ES-RO took 0.28107309341430664s
Availability | RDF dump link check for Apertium RDF ES-RO took 0.2736060619354248s
License | MR license check for Apertium RDF ES-RO took 0.2825744152069092s
License | HR license check for Apertium RDF ES-RO took 0.37905097007751465s
Amount of data | Number of property check for Apertium RDF ES-RO took 0.28344035148620605s
Understandability | Number of label check for Apertium RDF ES-RO took 0.338123083114624s
Understandability | URI regex check for Apertium RDF ES-RO took 0.5761256217956543s
Understandability | Vocabs check for Apertium RDF ES-RO took 0.2975921630859375s
Verifiability | Authors check for Apertium RDF ES-RO took 0.3271946907043457s
Verifiability | Publishers check for Apertium RDF ES-RO took 0.2831001281738281s
Performance | Throughput check for Apertium RDF ES-RO took 11.195769548416138s
Amount of data | Check the number of entities for Apertium RDF ES-RO took 9.059906005859375e-05s
Verifiability | Contribs. check for Apertium RDF ES-RO took 0.2755312919616699s
Interlinking | sameAs chians check for Apertium RDF ES-RO took 0.2745680809020996s
Interlinking | skos check for Apertium RDF ES-RO took 0.3044569492340088s
Interlinking | skos check for Apertium RDF ES-RO took 0.21927642822265625s
Timeliness | dataset update frequency check for Apertium RDF ES-RO took 0.2823672294616699s
Currency | Creation date check for Apertium RDF ES-RO took 0.4659249782562256s
Currency | Modification date check for Apertium RDF ES-RO took 0.29898881912231445s
Rep.Conc. | URIs length for Apertium RDF ES-RO took 92.33577036857605s
Interoperability | New vocabularies check for Apertium RDF ES-RO took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-RO took 0.30930137634277344s
Accuracy | Check Functional Property for Apertium RDF ES-RO took 0.27052855491638184s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-RO took 0.2769491672515869s
Accuracy | Check Empty annotation labels for Apertium RDF ES-RO took 0.8079278469085693s
Accuracy | Check White space in annotation for Apertium RDF ES-RO took 0.010152816772460938s
Accuracy | Check Datatype consistency for Apertium RDF ES-RO took 2.8195741176605225s
Consistency | Disjoint class check for Apertium RDF ES-RO took 0.2987384796142578s
Consistency | Check Misplaced properties for Apertium RDF ES-RO took 4.6125524044036865s
Consistency | Misplaced classes for Apertium RDF ES-RO took 8.912150382995605s
Consistency | Check Ontology hijacking for Apertium RDF ES-RO took 91.65643215179443s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-RO took 1.547438383102417s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-RO took 5.811461925506592s
Conciseness | Check Extensional conciseness for Apertium RDF ES-RO took 3.3144540786743164s
Conciseness | Check Intensional conciseness for Apertium RDF ES-RO took 0.32836270332336426s
Security | Sign check for Apertium RDF ES-RO took 0.31210851669311523s
Availability | Check URIs Dereferenciability for Apertium RDF ES-RO took 13.315359592437744s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.4622642993927002s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02139759063720703s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0009641647338867188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-RO took 2.6226043701171875e-06s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 647.072390794754s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 0.2225661277770996s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006322860717773438s
Extra | Recovery of all triples for Apertium RDF EU-EN took 263.52525877952576s
Performance | Total latancy measurement for Apertium RDF EU-EN took 1.336862325668335s
Amount of data | Number of triples check for Apertium RDF EU-EN took 2.167497158050537s
Interoperability | New terms check for Apertium RDF EU-EN took 3.289585828781128s
Versatility | Languages check for Apertium RDF EU-EN took 43.60904026031494s
Interpretability | Number of blank nodes check for Apertium RDF EU-EN took 1.0725736618041992s
Security | Check HTTPS for Apertium RDF EU-EN took 0.1337263584136963s
Interpretability | RDF structures check for Apertium RDF EU-EN took 0.30139613151550293s
Versatility | Serialization formats check for Apertium RDF EU-EN took 0.28109240531921387s
Availability | RDF dump link check for Apertium RDF EU-EN took 0.2735598087310791s
License | MR license check for Apertium RDF EU-EN took 0.31813573837280273s
License | HR license check for Apertium RDF EU-EN took 0.37242770195007324s
Amount of data | Number of property check for Apertium RDF EU-EN took 0.2790656089782715s
Understandability | Number of label check for Apertium RDF EU-EN took 0.3109722137451172s
Understandability | URI regex check for Apertium RDF EU-EN took 0.578697919845581s
Understandability | Vocabs check for Apertium RDF EU-EN took 0.2768571376800537s
Verifiability | Authors check for Apertium RDF EU-EN took 0.3172633647918701s
Verifiability | Publishers check for Apertium RDF EU-EN took 0.278670072555542s
Performance | Throughput check for Apertium RDF EU-EN took 11.224452495574951s
Amount of data | Check the number of entities for Apertium RDF EU-EN took 0.00013327598571777344s
Verifiability | Contribs. check for Apertium RDF EU-EN took 0.28647637367248535s
Interlinking | sameAs chians check for Apertium RDF EU-EN took 0.27440524101257324s
Interlinking | skos check for Apertium RDF EU-EN took 0.30085158348083496s
Interlinking | skos check for Apertium RDF EU-EN took 0.2325432300567627s
Timeliness | dataset update frequency check for Apertium RDF EU-EN took 0.28851914405822754s
Currency | Creation date check for Apertium RDF EU-EN took 0.27874040603637695s
Currency | Modification date check for Apertium RDF EU-EN took 0.2921180725097656s
Rep.Conc. | URIs length for Apertium RDF EU-EN took 90.42747664451599s
Interoperability | New vocabularies check for Apertium RDF EU-EN took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-EN took 0.29207897186279297s
Accuracy | Check Functional Property for Apertium RDF EU-EN took 0.29277968406677246s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-EN took 0.31007862091064453s
Accuracy | Check Empty annotation labels for Apertium RDF EU-EN took 0.8438918590545654s
Accuracy | Check White space in annotation for Apertium RDF EU-EN took 0.013931989669799805s
Accuracy | Check Datatype consistency for Apertium RDF EU-EN took 2.7498936653137207s
Consistency | Disjoint class check for Apertium RDF EU-EN took 0.28155946731567383s
Consistency | Check Misplaced properties for Apertium RDF EU-EN took 4.584366083145142s
Consistency | Misplaced classes for Apertium RDF EU-EN took 8.774729490280151s
Consistency | Check Ontology hijacking for Apertium RDF EU-EN took 91.15619540214539s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-EN took 1.5259299278259277s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-EN took 5.785346984863281s
Conciseness | Check Extensional conciseness for Apertium RDF EU-EN took 3.2672791481018066s
Conciseness | Check Intensional conciseness for Apertium RDF EU-EN took 0.31036877632141113s
Security | Sign check for Apertium RDF EU-EN took 0.2911996841430664s
Availability | Check URIs Dereferenciability for Apertium RDF EU-EN took 17.95480728149414s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 4.1348557472229s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.021111011505126953s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-EN took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 640.1448540687561s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 0.2226119041442871s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0005981922149658203s
Extra | Recovery of all triples for Apertium RDF EU-ES took 251.85845494270325s
Performance | Total latancy measurement for Apertium RDF EU-ES took 1.3394217491149902s
Amount of data | Number of triples check for Apertium RDF EU-ES took 2.1497340202331543s
Interoperability | New terms check for Apertium RDF EU-ES took 2.905245780944824s
Versatility | Languages check for Apertium RDF EU-ES took 43.70411252975464s
Interpretability | Number of blank nodes check for Apertium RDF EU-ES took 1.2373251914978027s
Security | Check HTTPS for Apertium RDF EU-ES took 0.13488173484802246s
Interpretability | RDF structures check for Apertium RDF EU-ES took 0.28577256202697754s
Versatility | Serialization formats check for Apertium RDF EU-ES took 0.27984619140625s
Availability | RDF dump link check for Apertium RDF EU-ES took 0.28925442695617676s
License | MR license check for Apertium RDF EU-ES took 0.2926304340362549s
License | HR license check for Apertium RDF EU-ES took 0.397350549697876s
Amount of data | Number of property check for Apertium RDF EU-ES took 0.27318477630615234s
Understandability | Number of label check for Apertium RDF EU-ES took 0.33566737174987793s
Understandability | URI regex check for Apertium RDF EU-ES took 0.5784759521484375s
Understandability | Vocabs check for Apertium RDF EU-ES took 0.29355692863464355s
Verifiability | Authors check for Apertium RDF EU-ES took 0.31888914108276367s
Verifiability | Publishers check for Apertium RDF EU-ES took 0.28220105171203613s
Performance | Throughput check for Apertium RDF EU-ES took 11.314286231994629s
Amount of data | Check the number of entities for Apertium RDF EU-ES took 9.322166442871094e-05s
Verifiability | Contribs. check for Apertium RDF EU-ES took 0.29327988624572754s
Interlinking | sameAs chians check for Apertium RDF EU-ES took 0.2867922782897949s
Interlinking | skos check for Apertium RDF EU-ES took 0.26924800872802734s
Interlinking | skos check for Apertium RDF EU-ES took 0.2533550262451172s
Timeliness | dataset update frequency check for Apertium RDF EU-ES took 0.2708139419555664s
Currency | Creation date check for Apertium RDF EU-ES took 0.28231000900268555s
Currency | Modification date check for Apertium RDF EU-ES took 0.3099672794342041s
Rep.Conc. | URIs length for Apertium RDF EU-ES took 95.23778676986694s
Interoperability | New vocabularies check for Apertium RDF EU-ES took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-ES took 0.3324904441833496s
Accuracy | Check Functional Property for Apertium RDF EU-ES took 0.28634190559387207s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-ES took 0.29274606704711914s
Accuracy | Check Empty annotation labels for Apertium RDF EU-ES took 0.8467714786529541s
Accuracy | Check White space in annotation for Apertium RDF EU-ES took 0.010262012481689453s
Accuracy | Check Datatype consistency for Apertium RDF EU-ES took 2.76986026763916s
Consistency | Disjoint class check for Apertium RDF EU-ES took 0.2840573787689209s
Consistency | Check Misplaced properties for Apertium RDF EU-ES took 4.722419500350952s
Consistency | Misplaced classes for Apertium RDF EU-ES took 8.738548517227173s
Consistency | Check Ontology hijacking for Apertium RDF EU-ES took 85.26514291763306s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-ES took 1.5371766090393066s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-ES took 5.917900562286377s
Conciseness | Check Extensional conciseness for Apertium RDF EU-ES took 3.37321138381958s
Conciseness | Check Intensional conciseness for Apertium RDF EU-ES took 0.3254578113555908s
Security | Sign check for Apertium RDF EU-ES took 0.3668956756591797s
Availability | Check URIs Dereferenciability for Apertium RDF EU-ES took 10.451182842254639s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.5758116245269775s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.021115779876708984s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 608.8837296962738s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.22185397148132324s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.000820159912109375s
Extra | Recovery of all triples for Apertium RDF FR-CA took 275.8588216304779s
Performance | Total latancy measurement for Apertium RDF FR-CA took 1.403397560119629s
Amount of data | Number of triples check for Apertium RDF FR-CA took 2.229283332824707s
Interoperability | New terms check for Apertium RDF FR-CA took 2.929020643234253s
Versatility | Languages check for Apertium RDF FR-CA took 43.60356163978577s
Interpretability | Number of blank nodes check for Apertium RDF FR-CA took 1.0755648612976074s
Security | Check HTTPS for Apertium RDF FR-CA took 0.14478778839111328s
Interpretability | RDF structures check for Apertium RDF FR-CA took 0.2877664566040039s
Versatility | Serialization formats check for Apertium RDF FR-CA took 0.2894303798675537s
Availability | RDF dump link check for Apertium RDF FR-CA took 0.2827000617980957s
License | MR license check for Apertium RDF FR-CA took 0.2812957763671875s
License | HR license check for Apertium RDF FR-CA took 0.35097599029541016s
Amount of data | Number of property check for Apertium RDF FR-CA took 0.2835659980773926s
Understandability | Number of label check for Apertium RDF FR-CA took 0.3175020217895508s
Understandability | URI regex check for Apertium RDF FR-CA took 0.5840678215026855s
Understandability | Vocabs check for Apertium RDF FR-CA took 0.29892468452453613s
Verifiability | Authors check for Apertium RDF FR-CA took 0.31801915168762207s
Verifiability | Publishers check for Apertium RDF FR-CA took 0.2873415946960449s
Performance | Throughput check for Apertium RDF FR-CA took 11.184061288833618s
Amount of data | Check the number of entities for Apertium RDF FR-CA took 0.00013589859008789062s
Verifiability | Contribs. check for Apertium RDF FR-CA took 0.2879829406738281s
Interlinking | sameAs chians check for Apertium RDF FR-CA took 0.2705087661743164s
Interlinking | skos check for Apertium RDF FR-CA took 0.3169562816619873s
Interlinking | skos check for Apertium RDF FR-CA took 0.22561907768249512s
Timeliness | dataset update frequency check for Apertium RDF FR-CA took 0.2700803279876709s
Currency | Creation date check for Apertium RDF FR-CA took 0.276843786239624s
Currency | Modification date check for Apertium RDF FR-CA took 0.29196643829345703s
Rep.Conc. | URIs length for Apertium RDF FR-CA took 86.20963048934937s
Interoperability | New vocabularies check for Apertium RDF FR-CA took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-CA took 0.30203866958618164s
Accuracy | Check Functional Property for Apertium RDF FR-CA took 0.285752534866333s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-CA took 0.28786134719848633s
Accuracy | Check Empty annotation labels for Apertium RDF FR-CA took 0.8372905254364014s
Accuracy | Check White space in annotation for Apertium RDF FR-CA took 0.01029062271118164s
Accuracy | Check Datatype consistency for Apertium RDF FR-CA took 2.7355592250823975s
Consistency | Disjoint class check for Apertium RDF FR-CA took 0.2933673858642578s
Consistency | Check Misplaced properties for Apertium RDF FR-CA took 4.665128231048584s
Consistency | Misplaced classes for Apertium RDF FR-CA took 8.795075416564941s
Consistency | Check Ontology hijacking for Apertium RDF FR-CA took 90.44680142402649s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-CA took 1.5228135585784912s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-CA took 5.740957975387573s
Conciseness | Check Extensional conciseness for Apertium RDF FR-CA took 3.252254009246826s
Conciseness | Check Intensional conciseness for Apertium RDF FR-CA took 0.31160569190979004s
Security | Sign check for Apertium RDF FR-CA took 0.2887277603149414s
Availability | Check URIs Dereferenciability for Apertium RDF FR-CA took 14.6975576877594s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.4711179733276367s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.027871131896972656s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-CA took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 636.6885397434235s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 0.2246837615966797s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006229877471923828s
Extra | Recovery of all triples for Apertium RDF FR-ES took 276.4928328990936s
Performance | Total latancy measurement for Apertium RDF FR-ES took 1.2446255683898926s
Amount of data | Number of triples check for Apertium RDF FR-ES took 2.430488348007202s
Interoperability | New terms check for Apertium RDF FR-ES took 2.8984014987945557s
Versatility | Languages check for Apertium RDF FR-ES took 43.66119194030762s
Interpretability | Number of blank nodes check for Apertium RDF FR-ES took 1.2491717338562012s
Security | Check HTTPS for Apertium RDF FR-ES took 0.12357163429260254s
Interpretability | RDF structures check for Apertium RDF FR-ES took 0.2802703380584717s
Versatility | Serialization formats check for Apertium RDF FR-ES took 0.27747511863708496s
Availability | RDF dump link check for Apertium RDF FR-ES took 0.28882789611816406s
License | MR license check for Apertium RDF FR-ES took 0.28039002418518066s
License | HR license check for Apertium RDF FR-ES took 0.37471723556518555s
Amount of data | Number of property check for Apertium RDF FR-ES took 0.2873704433441162s
Understandability | Number of label check for Apertium RDF FR-ES took 0.3105583190917969s
Understandability | URI regex check for Apertium RDF FR-ES took 0.5655174255371094s
Understandability | Vocabs check for Apertium RDF FR-ES took 0.2684338092803955s
Verifiability | Authors check for Apertium RDF FR-ES took 0.34416794776916504s
Verifiability | Publishers check for Apertium RDF FR-ES took 0.2685861587524414s
Performance | Throughput check for Apertium RDF FR-ES took 11.130321741104126s
Amount of data | Check the number of entities for Apertium RDF FR-ES took 8.869171142578125e-05s
Verifiability | Contribs. check for Apertium RDF FR-ES took 0.2651035785675049s
Interlinking | sameAs chians check for Apertium RDF FR-ES took 0.2841041088104248s
Interlinking | skos check for Apertium RDF FR-ES took 0.2784101963043213s
Interlinking | skos check for Apertium RDF FR-ES took 0.2427845001220703s
Timeliness | dataset update frequency check for Apertium RDF FR-ES took 0.35567164421081543s
Currency | Creation date check for Apertium RDF FR-ES took 0.2983081340789795s
Currency | Modification date check for Apertium RDF FR-ES took 0.28998708724975586s
Rep.Conc. | URIs length for Apertium RDF FR-ES took 85.84564685821533s
Interoperability | New vocabularies check for Apertium RDF FR-ES took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-ES took 2.1972687244415283s
Accuracy | Check Functional Property for Apertium RDF FR-ES took 0.30235910415649414s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-ES took 0.26828479766845703s
Accuracy | Check Empty annotation labels for Apertium RDF FR-ES took 0.8391973972320557s
Accuracy | Check White space in annotation for Apertium RDF FR-ES took 0.010227441787719727s
Accuracy | Check Datatype consistency for Apertium RDF FR-ES took 2.7185473442077637s
Consistency | Disjoint class check for Apertium RDF FR-ES took 0.29030776023864746s
Consistency | Check Misplaced properties for Apertium RDF FR-ES took 4.550054311752319s
Consistency | Misplaced classes for Apertium RDF FR-ES took 8.713336944580078s
Consistency | Check Ontology hijacking for Apertium RDF FR-ES took 90.62967157363892s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-ES took 1.5352087020874023s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-ES took 5.900981664657593s
Conciseness | Check Extensional conciseness for Apertium RDF FR-ES took 3.3582980632781982s
Conciseness | Check Intensional conciseness for Apertium RDF FR-ES took 0.32594990730285645s
Security | Sign check for Apertium RDF FR-ES took 0.2646811008453369s
Availability | Check URIs Dereferenciability for Apertium RDF FR-ES took 10.553008556365967s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.7665460109710693s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-ES took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 639.4784469604492s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 0.23853754997253418s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005786418914794922s
Extra | Recovery of all triples for Apertium RDF OC-CA took 263.9592373371124s
Performance | Total latancy measurement for Apertium RDF OC-CA took 1.2580170631408691s
Amount of data | Number of triples check for Apertium RDF OC-CA took 2.1400065422058105s
Interoperability | New terms check for Apertium RDF OC-CA took 2.900252103805542s
Versatility | Languages check for Apertium RDF OC-CA took 43.53378963470459s
Interpretability | Number of blank nodes check for Apertium RDF OC-CA took 1.0649690628051758s
Security | Check HTTPS for Apertium RDF OC-CA took 0.14538884162902832s
Interpretability | RDF structures check for Apertium RDF OC-CA took 0.3042733669281006s
Versatility | Serialization formats check for Apertium RDF OC-CA took 0.27210354804992676s
Availability | RDF dump link check for Apertium RDF OC-CA took 0.2768268585205078s
License | MR license check for Apertium RDF OC-CA took 0.28228044509887695s
License | HR license check for Apertium RDF OC-CA took 0.36467647552490234s
Amount of data | Number of property check for Apertium RDF OC-CA took 0.27411389350891113s
Understandability | Number of label check for Apertium RDF OC-CA took 0.3223867416381836s
Understandability | URI regex check for Apertium RDF OC-CA took 0.5882275104522705s
Understandability | Vocabs check for Apertium RDF OC-CA took 0.27968311309814453s
Verifiability | Authors check for Apertium RDF OC-CA took 0.336284875869751s
Verifiability | Publishers check for Apertium RDF OC-CA took 0.28181982040405273s
Performance | Throughput check for Apertium RDF OC-CA took 11.189247846603394s
Amount of data | Check the number of entities for Apertium RDF OC-CA took 9.72747802734375e-05s
Verifiability | Contribs. check for Apertium RDF OC-CA took 0.2801392078399658s
Interlinking | sameAs chians check for Apertium RDF OC-CA took 0.27169084548950195s
Interlinking | skos check for Apertium RDF OC-CA took 0.2641420364379883s
Interlinking | skos check for Apertium RDF OC-CA took 0.2261216640472412s
Timeliness | dataset update frequency check for Apertium RDF OC-CA took 0.29564666748046875s
Currency | Creation date check for Apertium RDF OC-CA took 0.2839622497558594s
Currency | Modification date check for Apertium RDF OC-CA took 0.27486085891723633s
Rep.Conc. | URIs length for Apertium RDF OC-CA took 87.13974809646606s
Interoperability | New vocabularies check for Apertium RDF OC-CA took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-CA took 0.3218841552734375s
Accuracy | Check Functional Property for Apertium RDF OC-CA took 0.2665534019470215s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-CA took 0.28160834312438965s
Accuracy | Check Empty annotation labels for Apertium RDF OC-CA took 0.8543660640716553s
Accuracy | Check White space in annotation for Apertium RDF OC-CA took 0.010363578796386719s
Accuracy | Check Datatype consistency for Apertium RDF OC-CA took 2.758061408996582s
Consistency | Disjoint class check for Apertium RDF OC-CA took 0.27713751792907715s
Consistency | Check Misplaced properties for Apertium RDF OC-CA took 4.610522747039795s
Consistency | Misplaced classes for Apertium RDF OC-CA took 8.830293893814087s
Consistency | Check Ontology hijacking for Apertium RDF OC-CA took 86.26358461380005s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-CA took 1.5625176429748535s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-CA took 5.691091775894165s
Conciseness | Check Extensional conciseness for Apertium RDF OC-CA took 3.244870662689209s
Conciseness | Check Intensional conciseness for Apertium RDF OC-CA took 0.32741737365722656s
Security | Sign check for Apertium RDF OC-CA took 0.3279998302459717s
Availability | Check URIs Dereferenciability for Apertium RDF OC-CA took 16.820296049118042s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 1.492462158203125s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.021329164505004883s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0008320808410644531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-CA took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 633.2853829860687s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 0.24000024795532227s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0007519721984863281s
Extra | Recovery of all triples for Apertium RDF OC-ES took 262.39958572387695s
Performance | Total latancy measurement for Apertium RDF OC-ES took 1.371415376663208s
Amount of data | Number of triples check for Apertium RDF OC-ES took 2.0863635540008545s
Interoperability | New terms check for Apertium RDF OC-ES took 3.10481595993042s
Versatility | Languages check for Apertium RDF OC-ES took 43.65333652496338s
Interpretability | Number of blank nodes check for Apertium RDF OC-ES took 1.0803191661834717s
Security | Check HTTPS for Apertium RDF OC-ES took 0.13375449180603027s
Interpretability | RDF structures check for Apertium RDF OC-ES took 0.294938325881958s
Versatility | Serialization formats check for Apertium RDF OC-ES took 0.28186988830566406s
Availability | RDF dump link check for Apertium RDF OC-ES took 0.2865898609161377s
License | MR license check for Apertium RDF OC-ES took 0.28406429290771484s
License | HR license check for Apertium RDF OC-ES took 0.36124706268310547s
Amount of data | Number of property check for Apertium RDF OC-ES took 0.27495312690734863s
Understandability | Number of label check for Apertium RDF OC-ES took 0.32466769218444824s
Understandability | URI regex check for Apertium RDF OC-ES took 0.5545973777770996s
Understandability | Vocabs check for Apertium RDF OC-ES took 0.27332639694213867s
Verifiability | Authors check for Apertium RDF OC-ES took 0.32452988624572754s
Verifiability | Publishers check for Apertium RDF OC-ES took 0.31072258949279785s
Performance | Throughput check for Apertium RDF OC-ES took 11.33284330368042s
Amount of data | Check the number of entities for Apertium RDF OC-ES took 4.1961669921875e-05s
Verifiability | Contribs. check for Apertium RDF OC-ES took 0.2881748676300049s
Interlinking | sameAs chians check for Apertium RDF OC-ES took 0.26173877716064453s
Interlinking | skos check for Apertium RDF OC-ES took 0.2635385990142822s
Interlinking | skos check for Apertium RDF OC-ES took 0.251492977142334s
Timeliness | dataset update frequency check for Apertium RDF OC-ES took 0.28576135635375977s
Currency | Creation date check for Apertium RDF OC-ES took 0.28252363204956055s
Currency | Modification date check for Apertium RDF OC-ES took 0.280529260635376s
Rep.Conc. | URIs length for Apertium RDF OC-ES took 89.8367018699646s
Interoperability | New vocabularies check for Apertium RDF OC-ES took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-ES took 0.3096194267272949s
Accuracy | Check Functional Property for Apertium RDF OC-ES took 0.3152289390563965s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-ES took 0.2992095947265625s
Accuracy | Check Empty annotation labels for Apertium RDF OC-ES took 0.8071520328521729s
Accuracy | Check White space in annotation for Apertium RDF OC-ES took 0.010851860046386719s
Accuracy | Check Datatype consistency for Apertium RDF OC-ES took 2.8781375885009766s
Consistency | Disjoint class check for Apertium RDF OC-ES took 0.27591824531555176s
Consistency | Check Misplaced properties for Apertium RDF OC-ES took 4.597162485122681s
Consistency | Misplaced classes for Apertium RDF OC-ES took 8.775613069534302s
Consistency | Check Ontology hijacking for Apertium RDF OC-ES took 90.87769174575806s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-ES took 1.5315210819244385s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-ES took 5.702287435531616s
Conciseness | Check Extensional conciseness for Apertium RDF OC-ES took 3.264741897583008s
Conciseness | Check Intensional conciseness for Apertium RDF OC-ES took 0.3146331310272217s
Security | Sign check for Apertium RDF OC-ES took 0.268768310546875s
Availability | Check URIs Dereferenciability for Apertium RDF OC-ES took 9.90260100364685s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 1.8432905673980713s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020977497100830078s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-ES took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF OC-ES took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 637.9165654182434s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 0.2280595302581787s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.00035381317138671875s
Extra | Recovery of all triples for Apertium RDF PT-CA took 265.8427414894104s
Performance | Total latancy measurement for Apertium RDF PT-CA took 1.2426929473876953s
Amount of data | Number of triples check for Apertium RDF PT-CA took 2.209627628326416s
Interoperability | New terms check for Apertium RDF PT-CA took 2.8776164054870605s
Versatility | Languages check for Apertium RDF PT-CA took 43.70945978164673s
Interpretability | Number of blank nodes check for Apertium RDF PT-CA took 1.0909371376037598s
Security | Check HTTPS for Apertium RDF PT-CA took 0.1356678009033203s
Interpretability | RDF structures check for Apertium RDF PT-CA took 0.29421353340148926s
Versatility | Serialization formats check for Apertium RDF PT-CA took 0.2801089286804199s
Availability | RDF dump link check for Apertium RDF PT-CA took 0.2908787727355957s
License | MR license check for Apertium RDF PT-CA took 0.2683401107788086s
License | HR license check for Apertium RDF PT-CA took 0.35245752334594727s
Amount of data | Number of property check for Apertium RDF PT-CA took 0.29378294944763184s
Understandability | Number of label check for Apertium RDF PT-CA took 0.3147604465484619s
Understandability | URI regex check for Apertium RDF PT-CA took 0.5614664554595947s
Understandability | Vocabs check for Apertium RDF PT-CA took 0.2908623218536377s
Verifiability | Authors check for Apertium RDF PT-CA took 0.31076884269714355s
Verifiability | Publishers check for Apertium RDF PT-CA took 0.28689050674438477s
Performance | Throughput check for Apertium RDF PT-CA took 11.21028470993042s
Amount of data | Check the number of entities for Apertium RDF PT-CA took 9.298324584960938e-05s
Verifiability | Contribs. check for Apertium RDF PT-CA took 0.29461169242858887s
Interlinking | sameAs chians check for Apertium RDF PT-CA took 0.26976823806762695s
Interlinking | skos check for Apertium RDF PT-CA took 0.2946169376373291s
Interlinking | skos check for Apertium RDF PT-CA took 0.22615456581115723s
Timeliness | dataset update frequency check for Apertium RDF PT-CA took 0.2914881706237793s
Currency | Creation date check for Apertium RDF PT-CA took 0.28200268745422363s
Currency | Modification date check for Apertium RDF PT-CA took 0.28298330307006836s
Rep.Conc. | URIs length for Apertium RDF PT-CA took 93.83266806602478s
Interoperability | New vocabularies check for Apertium RDF PT-CA took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-CA took 0.329693078994751s
Accuracy | Check Functional Property for Apertium RDF PT-CA took 0.2823176383972168s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-CA took 0.29052019119262695s
Accuracy | Check Empty annotation labels for Apertium RDF PT-CA took 0.8542542457580566s
Accuracy | Check White space in annotation for Apertium RDF PT-CA took 0.010242223739624023s
Accuracy | Check Datatype consistency for Apertium RDF PT-CA took 2.768810987472534s
Consistency | Disjoint class check for Apertium RDF PT-CA took 0.2765176296234131s
Consistency | Check Misplaced properties for Apertium RDF PT-CA took 4.5826356410980225s
Consistency | Misplaced classes for Apertium RDF PT-CA took 8.868470430374146s
Consistency | Check Ontology hijacking for Apertium RDF PT-CA took 90.95822095870972s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-CA took 1.5173542499542236s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-CA took 5.860041379928589s
Conciseness | Check Extensional conciseness for Apertium RDF PT-CA took 3.2992746829986572s
Conciseness | Check Intensional conciseness for Apertium RDF PT-CA took 0.31134033203125s
Security | Sign check for Apertium RDF PT-CA took 0.29784488677978516s
Availability | Check URIs Dereferenciability for Apertium RDF PT-CA took 9.79189682006836s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 3.01745343208313s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02154541015625s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-CA took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 643.6805500984192s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 0.21217870712280273s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0008053779602050781s
Extra | Recovery of all triples for Apertium RDF PT-GL took 277.6509096622467s
Performance | Total latancy measurement for Apertium RDF PT-GL took 1.242110013961792s
Amount of data | Number of triples check for Apertium RDF PT-GL took 2.136133909225464s
Interoperability | New terms check for Apertium RDF PT-GL took 2.9038541316986084s
Versatility | Languages check for Apertium RDF PT-GL took 43.6877977848053s
Interpretability | Number of blank nodes check for Apertium RDF PT-GL took 1.2117700576782227s
Security | Check HTTPS for Apertium RDF PT-GL took 0.18234992027282715s
Interpretability | RDF structures check for Apertium RDF PT-GL took 0.2982666492462158s
Versatility | Serialization formats check for Apertium RDF PT-GL took 0.28975510597229004s
Availability | RDF dump link check for Apertium RDF PT-GL took 0.27161264419555664s
License | MR license check for Apertium RDF PT-GL took 0.30118274688720703s
License | HR license check for Apertium RDF PT-GL took 0.3524031639099121s
Amount of data | Number of property check for Apertium RDF PT-GL took 0.2859036922454834s
Understandability | Number of label check for Apertium RDF PT-GL took 0.32050490379333496s
Understandability | URI regex check for Apertium RDF PT-GL took 0.5567281246185303s
Understandability | Vocabs check for Apertium RDF PT-GL took 0.2908763885498047s
Verifiability | Authors check for Apertium RDF PT-GL took 0.321561336517334s
Verifiability | Publishers check for Apertium RDF PT-GL took 0.2906157970428467s
Performance | Throughput check for Apertium RDF PT-GL took 11.250558853149414s
Amount of data | Check the number of entities for Apertium RDF PT-GL took 9.131431579589844e-05s
Verifiability | Contribs. check for Apertium RDF PT-GL took 0.30247044563293457s
Interlinking | sameAs chians check for Apertium RDF PT-GL took 0.2704782485961914s
Interlinking | skos check for Apertium RDF PT-GL took 0.2941434383392334s
Interlinking | skos check for Apertium RDF PT-GL took 0.2243938446044922s
Timeliness | dataset update frequency check for Apertium RDF PT-GL took 0.27689242362976074s
Currency | Creation date check for Apertium RDF PT-GL took 0.28598666191101074s
Currency | Modification date check for Apertium RDF PT-GL took 0.27638792991638184s
Rep.Conc. | URIs length for Apertium RDF PT-GL took 90.31314134597778s
Interoperability | New vocabularies check for Apertium RDF PT-GL took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-GL took 0.3220632076263428s
Accuracy | Check Functional Property for Apertium RDF PT-GL took 0.32131314277648926s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-GL took 0.2800171375274658s
Accuracy | Check Empty annotation labels for Apertium RDF PT-GL took 0.8571493625640869s
Accuracy | Check White space in annotation for Apertium RDF PT-GL took 0.010325431823730469s
Accuracy | Check Datatype consistency for Apertium RDF PT-GL took 2.747108221054077s
Consistency | Disjoint class check for Apertium RDF PT-GL took 0.27990221977233887s
Consistency | Check Misplaced properties for Apertium RDF PT-GL took 4.657505750656128s
Consistency | Misplaced classes for Apertium RDF PT-GL took 8.753814935684204s
Consistency | Check Ontology hijacking for Apertium RDF PT-GL took 96.26648020744324s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-GL took 1.5335569381713867s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-GL took 5.826805591583252s
Conciseness | Check Extensional conciseness for Apertium RDF PT-GL took 3.279616117477417s
Conciseness | Check Intensional conciseness for Apertium RDF PT-GL took 0.3108963966369629s
Security | Sign check for Apertium RDF PT-GL took 0.298459529876709s
Availability | Check URIs Dereferenciability for Apertium RDF PT-GL took 13.346267938613892s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 171.37976717948914s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02139139175415039s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-GL took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 901.6255261898041s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.5283048152923584s
Availability | VoID file availability check for AragoDBPedia took 0.0005977153778076172s
Extra | Recovery of all triples for AragoDBPedia took 4.012775897979736s
Performance | Total latancy measurement for AragoDBPedia took 1.5315921306610107s
Amount of data | Number of triples check for AragoDBPedia took 0.7441716194152832s
Interoperability | New terms check for AragoDBPedia took 2.1005029678344727s
Versatility | Languages check for AragoDBPedia took 60.39170289039612s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.2164306640625s
Security | Check HTTPS for AragoDBPedia took 0.2110919952392578s
Interpretability | RDF structures check for AragoDBPedia took 0.67533278465271s
Versatility | Serialization formats check for AragoDBPedia took 0.3491485118865967s
Availability | RDF dump link check for AragoDBPedia took 0.34863972663879395s
License | MR license check for AragoDBPedia took 0.6085207462310791s
License | HR license check for AragoDBPedia took 5.757411003112793s
Amount of data | Number of property check for AragoDBPedia took 0.3411905765533447s
Understandability | Number of label check for AragoDBPedia took 0.4586150646209717s
Understandability | URI regex check for AragoDBPedia took 0.7727088928222656s
Understandability | Vocabs check for AragoDBPedia took 0.3627748489379883s
Verifiability | Authors check for AragoDBPedia took 0.6899352073669434s
Verifiability | Publishers check for AragoDBPedia took 0.3720395565032959s
Performance | Throughput check for AragoDBPedia took 12.224551916122437s
Amount of data | Check the number of entities for AragoDBPedia took 9.179115295410156e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.4235720634460449s
Interlinking | sameAs chians check for AragoDBPedia took 0.3531057834625244s
Interlinking | skos check for AragoDBPedia took 0.5358290672302246s
Interlinking | skos check for AragoDBPedia took 0.30150628089904785s
Timeliness | dataset update frequency check for AragoDBPedia took 0.4223923683166504s
Currency | Creation date check for AragoDBPedia took 0.3512599468231201s
Currency | Modification date check for AragoDBPedia took 0.7058641910552979s
Rep.Conc. | URIs length for AragoDBPedia took 5.800469636917114s
Interoperability | New vocabularies check for AragoDBPedia took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.34531164169311523s
Accuracy | Check Functional Property for AragoDBPedia took 0.4534785747528076s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.4033207893371582s
Accuracy | Check Empty annotation labels for AragoDBPedia took 0.9387869834899902s
Accuracy | Check White space in annotation for AragoDBPedia took 0.03099846839904785s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.029126882553100586s
Consistency | Disjoint class check for AragoDBPedia took 0.33852314949035645s
Consistency | Check Misplaced properties for AragoDBPedia took 4.186868906021118s
Consistency | Misplaced classes for AragoDBPedia took 0.5616686344146729s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.5605499744415283s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.4650366306304932s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.415720701217651s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03643536567687988s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.496335506439209s
Security | Sign check for AragoDBPedia took 0.5196013450622559s
Availability | Check URIs Dereferenciability for AragoDBPedia took 2749.479311466217s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 120.06477403640747s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.022021055221557617s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0009503364562988281s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for AragoDBPedia took 1.1682510375976562e-05s
INFO | --- Analysis for aragodbpedia took 3233.9254751205444s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.341848850250244s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.3071877956390381s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.021439790725708008s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.626678466796875e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for archiveshub-linkeddata took 303.5674982070923s
Availability | SPARQL endpoint availability check for Archivi ISMA took 30.120521068572998s
Availability | VoID file availability check for Archivi ISMA took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.44002556800842285s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.021342754364013672s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.4332275390625e-05s
Believability | Calculation of trust value for Archivi ISMA took 1.239776611328125e-05s
INFO | --- Analysis for archivio-isma took 316.0225052833557s
Availability | SPARQL endpoint availability check for ARIADNE took 0.3479459285736084s
Availability | VoID file availability check for ARIADNE took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for ARIADNE took 56.25983810424805s
Reputation | Calculation of the PageRank for ARIADNE took 0.023430347442626953s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.001575469970703125s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 6.67572021484375e-05s
Believability | Calculation of trust value for ARIADNE took 7.3909759521484375e-06s
INFO | --- Analysis for ariadne took 405.79581117630005s
Availability | SPARQL endpoint availability check for Aristotle University took 8.320808410644531e-05s
Availability | VoID file availability check for Aristotle University took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Aristotle University took 117.40199327468872s
Reputation | Calculation of the PageRank for Aristotle University took 0.02153754234313965s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 4.839897155761719e-05s
Believability | Calculation of trust value for Aristotle University took 1.2159347534179688e-05s
INFO | --- Analysis for aristotle-university took 478.88438963890076s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.63590407371521s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 25.452818393707275s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.0517578125e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.1205673217773438e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 88.55377101898193s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.267692565917969e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 15.210033178329468s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.02120375633239746s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.239776611328125e-05s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 52.430325508117676s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.965141773223877s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0003333091735839844s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.4936823844909668s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.022224903106689453s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.0531158447265625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.239776611328125e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 37.05591869354248s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 8.940696716308594e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.3238525390625s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.021821022033691406s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0010025501251220703s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0001232624053955078s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.1205673217773438e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 12.401884317398071s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.7206878662109375e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 2.821093797683716s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02090930938720703s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00011157989501953125s
Believability | Calculation of trust value for Arthroscopy community took 1.430511474609375e-05s
INFO | --- Analysis for arthroscopy took 36.61658072471619s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.452946424484253s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.3487985134124756s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.022081613540649414s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.106231689453125e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 20.607202291488647s
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.3724918365478516s
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.0006418228149414062s
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 2.0329461097717285s
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.02493906021118164s
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.3828277587890625e-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.0011603832244873047s
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 0.0001125335693359375s
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 14.72254204750061s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.416302442550659s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.0564422607421875s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.021867752075195312s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0010404586791992188s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.00011086463928222656s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 20.72489619255066s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.3831818103790283s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0009675025939941406s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 2.0027663707733154s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02651190757751465s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0015103816986083984s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 6.079673767089844e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.4543533325195312e-05s
INFO | --- Analysis for ASCDC-CRB took 21.37142515182495s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.3858485221862793s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 3.2348692417144775s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020999908447265625s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.274482727050781e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 23.731840133666992s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.411741256713867s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 17.83182644844055s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.647804260253906e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-DQOT took 83.34486198425293s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.4190409183502197s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.535718202590942s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02147197723388672s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0008122920989990234s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.630752563476562e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 62.580692291259766s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.1995816230773926s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 2.2616403102874756s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.963180541992188e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 20.1543288230896s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.382739782333374s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.9843881130218506s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.5789947509765625e-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.1682510375976562e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 18.019240617752075s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.392852783203125s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 6.318840265274048s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.021070480346679688s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.459785461425781e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 17.725037097930908s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.918501853942871s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.3267374038696289s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020928621292114258s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.744529724121094e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 17.818662881851196s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.3835906982421875s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.5540053844451904s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.107589721679688e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 13.949062585830688s
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.381221294403076s
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.0006279945373535156s
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 2.3350441455841064s
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.03192257881164551s
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.5735626220703125e-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.0012791156768798828s
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 0.00012183189392089844s
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.2636184692382812e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 17.368496894836426s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.3787083625793457s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 2.080124616622925s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02399921417236328s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0013408660888671875s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 7.200241088867188e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC_-_DNB took 15.23606538772583s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 8.58306884765625e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 1.538954496383667s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.461143493652344e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.2874603271484375e-05s
INFO | --- Analysis for asit took 12.953949451446533s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 0.0001068115234375s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 1.9519286155700684s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02164626121520996s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.4345855712890625e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.2874603271484375e-05s
INFO | --- Analysis for asjp took 7.834136247634888s
Availability | SPARQL endpoint availability check for ASN:US took 265.43694162368774s
Availability | VoID file availability check for ASN:US took 0.0007867813110351562s
Completeness | Calculation of interlinking completeness for ASN:US took 3.849846839904785s
Reputation | Calculation of the PageRank for ASN:US took 0.021284818649291992s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.343292236328125e-05s
Believability | Calculation of trust value for ASN:US took 1.239776611328125e-05s
INFO | --- Analysis for asn-us took 422.03419160842896s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 8.893013000488281e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.44931650161743164s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020768404006958008s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.123283386230469e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 8.344650268554688e-06s
INFO | --- Analysis for aspire-mmu took 11.998646020889282s
Availability | SPARQL endpoint availability check for associations took 8.916854858398438e-05s
Availability | VoID file availability check for associations took 1.0187339782714844s
Completeness | Calculation of interlinking completeness for associations took 0.48760986328125s
Reputation | Calculation of the PageRank for associations took 0.021365880966186523s
Interlinking | Calculation of Degree of Connection for associations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for associations took 0.0008287429809570312s
Interlinking | Calculation of Clustering coefficient for associations took 7.748603820800781e-05s
Interoperability | Check the re-using of existing vocabs for associations took 3.4369759559631348s
Believability | Calculation of trust value for associations took 1.1682510375976562e-05s
INFO | --- Analysis for associations took 18.06632900238037s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 0.18062305450439453s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 2.9540255069732666s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.0279159545898438e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.0728836059570312e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 9.01158332824707s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 9.703636169433594e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.30959105491638184s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02142477035522461s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.703636169433594e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.2159347534179688e-05s
INFO | --- Analysis for athelia-rfid took 10.12749457359314s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.586815357208252s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0008270740509033203s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.3716869354248047s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.02122950553894043s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.933906555175781e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for aueb-linked-open-data took 18.958414316177368s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.632990837097168s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.4854154586791992s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.023485898971557617s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.0067901611328125e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for AugustiniConfessiones took 11.622275352478027s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5672492980957031s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0013341903686523438s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.3080563545227051s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02099156379699707s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.250640869140625e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.239776611328125e-05s
INFO | --- Analysis for austrian_ski_racers took 10.512898683547974s
Availability | SPARQL endpoint availability check for AVsOnto took 9.012222290039062e-05s
Availability | VoID file availability check for AVsOnto took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for AVsOnto took 5.586401462554932s
Reputation | Calculation of the PageRank for AVsOnto took 0.022187471389770508s
Interlinking | Calculation of Degree of Connection for AVsOnto took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0010325908660888672s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.528594970703125e-05s
Believability | Calculation of trust value for AVsOnto took 1.2636184692382812e-05s
INFO | --- Analysis for AVsOnto took 12.577699422836304s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20356035232543945s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23779702186584473s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 61.36909627914429s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.6864981651306152s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.09307408332825s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.4835076332092285s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.103866815567s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.074903011322s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23505377769470215s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1797013282775879s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14034128189086914s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10387516021728516s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 123.68120551109314s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0872573852539s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14219427108764648s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1039023399353s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23341679573059082s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10805583000183105s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 152.65663743019104s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 144.63827538490295s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.544184446334839s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00011110305786132812s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 59.9705171585083s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 299.6209897994995s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15165185928344727s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13130593299865723s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13461017608642578s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 210.32619881629944s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2410585880279541s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 90.64633536338806s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14719343185424805s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 17.689237594604492s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.436856746673584s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.7031941413879395s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1433877944946289s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.6424875259399414s
Consistency | Misplaced classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.881142616271973s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.391628742218018s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 21748.492772340775s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.8049147129058838s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.3950066566467285s
Conciseness | Check Intensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1365828514099121s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1322014331817627s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9479162693023682s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 60.3123517036438s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02323293685913086s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0011670589447021484s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.384185791015625e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.049041748046875e-05s
INFO | --- Analysis for b3kat took 25752.379804849625s
Availability | SPARQL endpoint availability check for BabelNet took 0.4341104030609131s
Availability | VoID file availability check for BabelNet took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for BabelNet took 180.2436399459839s
Reputation | Calculation of the PageRank for BabelNet took 0.02438950538635254s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0010595321655273438s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0002071857452392578s
Believability | Calculation of trust value for BabelNet took 1.3113021850585938e-05s
INFO | --- Analysis for babelnet took 287.0999348163605s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 0.00010466575622558594s
Availability | VoID file availability check for Bacevicius.lt took 0.0003948211669921875s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 6.920861482620239s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.02306199073791504s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.001233816146850586s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 5.412101745605469e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.621246337890625e-05s
INFO | --- Analysis for Bacevicius.lt took 501.76356625556946s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.560326337814331s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.3746058940887451s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.022736549377441406s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.2438507080078125e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.1920928955078125e-05s
INFO | --- Analysis for bag took 244.03984308242798s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.30030035972595215s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.32251477241516113s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02187943458557129s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.9577484130859375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.3113021850585938e-05s
INFO | --- Analysis for baixue took 361.68185210227966s
Availability | SPARQL endpoint availability check for baixue composer took 8.916854858398438e-05s
Availability | VoID file availability check for baixue composer took 0.00128936767578125s
Completeness | Calculation of interlinking completeness for baixue composer took 0.32241296768188477s
Reputation | Calculation of the PageRank for baixue composer took 0.02157425880432129s
Interlinking | Calculation of Degree of Connection for baixue composer took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.075599670410156e-05s
Believability | Calculation of trust value for baixue composer took 1.1444091796875e-05s
INFO | --- Analysis for baixue_composer took 3.5367960929870605s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.511543273925781e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.3230314254760742s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.022414445877075195s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0011148452758789062s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.9577484130859375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.239776611328125e-05s
INFO | --- Analysis for baixue_imagery took 242.56874871253967s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.083747863769531e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.3111698627471924s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021351099014282227s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.956390380859375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.239776611328125e-05s
INFO | --- Analysis for baixue_imagery1 took 3.820671319961548s
Availability | SPARQL endpoint availability check for BAMS took 8.7738037109375e-05s
Availability | VoID file availability check for BAMS took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for BAMS took 0.6504111289978027s
Reputation | Calculation of the PageRank for BAMS took 0.021080493927001953s
Interlinking | Calculation of Degree of Connection for BAMS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.790855407714844e-05s
Believability | Calculation of trust value for BAMS took 1.2159347534179688e-05s
INFO | --- Analysis for bams took 11.210206270217896s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 6.818771362304688e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 60.12705659866333s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.023450136184692383s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.239776611328125e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 123.0534029006958s
Availability | SPARQL endpoint availability check for BBC Music took 0.46900200843811035s
Availability | VoID file availability check for BBC Music took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for BBC Music took 3.2092559337615967s
Reputation | Calculation of the PageRank for BBC Music took 0.021060943603515625s
Interlinking | Calculation of Degree of Connection for BBC Music took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Music took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013446807861328125s
Believability | Calculation of trust value for BBC Music took 1.239776611328125e-05s
INFO | --- Analysis for bbc-music took 255.26723265647888s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.27043890953063965s
Availability | VoID file availability check for BBC Programmes took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for BBC Programmes took 61.05723452568054s
Reputation | Calculation of the PageRank for BBC Programmes took 0.022373199462890625s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00011014938354492188s
Believability | Calculation of trust value for BBC Programmes took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-programmes took 199.85442233085632s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.3369882106781006s
Availability | VoID file availability check for BBC Wildlife Finder took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 59.89552617073059s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02145671844482422s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010371208190917969s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.239776611328125e-05s
INFO | --- Analysis for bbc-wildlife-finder took 72.81711554527283s
Availability | SPARQL endpoint availability check for BBOP took 8.821487426757812e-05s
Availability | VoID file availability check for BBOP took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for BBOP took 65.04660820960999s
Reputation | Calculation of the PageRank for BBOP took 0.021964073181152344s
Interlinking | Calculation of Degree of Connection for BBOP took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0010328292846679688s
Interlinking | Calculation of Clustering coefficient for BBOP took 4.5299530029296875e-05s
Believability | Calculation of trust value for BBOP took 1.9311904907226562e-05s
INFO | --- Analysis for bbop took 228.86915230751038s
Availability | SPARQL endpoint availability check for BBOP took 8.559226989746094e-05s
Availability | VoID file availability check for BBOP took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for BBOP took 0.8130824565887451s
Reputation | Calculation of the PageRank for BBOP took 0.02112746238708496s
Interlinking | Calculation of Degree of Connection for BBOP took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.8623809814453125e-05s
Believability | Calculation of trust value for BBOP took 1.2159347534179688e-05s
INFO | --- Analysis for bbop-selected took 205.41556191444397s
Availability | SPARQL endpoint availability check for Bdgp took 1.1088008880615234s
Availability | VoID file availability check for Bdgp took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for Bdgp took 60.28585171699524s
Reputation | Calculation of the PageRank for Bdgp took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Bdgp took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bdgp took 1.2636184692382812e-05s
INFO | --- Analysis for bdgp took 123.73908376693726s
Availability | SPARQL endpoint availability check for Bendev Junior took 8.940696716308594e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.3876171112060547s
Reputation | Calculation of the PageRank for Bendev Junior took 0.02752089500427246s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0014770030975341797s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 5.125999450683594e-05s
Believability | Calculation of trust value for Bendev Junior took 7.867813110351562e-06s
INFO | --- Analysis for bendevoficial took 121.69191670417786s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 2.2853896617889404s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 59.62974762916565s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.021327733993530273s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.319450378417969e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.245208740234375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 189.48363399505615s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 9.179115295410156e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.30574488639831543s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.023009061813354492s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.123283386230469e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 6.67572021484375e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.413815975189209s
Availability | SPARQL endpoint availability check for berlios took 0.00010967254638671875s
Availability | VoID file availability check for berlios took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for berlios took 0.94089674949646s
Reputation | Calculation of the PageRank for berlios took 0.02134227752685547s
Interlinking | Calculation of Degree of Connection for berlios took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for berlios took 8.845329284667969e-05s
Believability | Calculation of trust value for berlios took 1.1920928955078125e-05s
INFO | --- Analysis for berlios took 122.70011281967163s
Availability | SPARQL endpoint availability check for Between Our Worlds took 7.796287536621094e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.5891132354736328s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.021175384521484375s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.937980651855469e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.2636184692382812e-05s
INFO | --- Analysis for betweenourworlds took 69.19296407699585s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.09829044342041016s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.9943275451660156s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.34600830078125e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for bfs-linked-data took 64.39886617660522s
Availability | SPARQL endpoint availability check for BibBase took 0.16665887832641602s
Availability | VoID file availability check for BibBase took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for BibBase took 0.3258960247039795s
Reputation | Calculation of the PageRank for BibBase took 0.02111959457397461s
Interlinking | Calculation of Degree of Connection for BibBase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0008101463317871094s
Interlinking | Calculation of Clustering coefficient for BibBase took 0.00010585784912109375s
Believability | Calculation of trust value for BibBase took 1.1920928955078125e-05s
INFO | --- Analysis for bibbase took 123.74664568901062s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 9.751319885253906e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0008323192596435547s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.5951693058013916s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00010561943054199219s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.1920928955078125e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 132.39396286010742s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.00010061264038085938s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.3680260181427002s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.021225690841674805s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0009114742279052734s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.0001373291015625s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.3113021850585938e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 128.52138018608093s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.267692565917969e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 60.3173189163208s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.022695064544677734s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0009775161743164062s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.7670135498046875e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 123.95948886871338s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 8.869171142578125e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 59.589152097702026s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02171015739440918s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.52587890625e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 4.315376281738281e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.1682510375976562e-05s
INFO | --- Analysis for BibSonomy took 257.20293283462524s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 9.1552734375e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0008053779602050781s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 60.31973338127136s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.02103400230407715s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.9802322387695312e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 7.152557373046875e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 90.98979449272156s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 8.797645568847656e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 1.5984914302825928s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.0211637020111084s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007636547088623047s
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.239776611328125e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 3.774064302444458s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 1.2134134769439697s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.3477363586425781s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.86102294921875e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-acfsid took 13.73065972328186s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 0.25296545028686523s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005786418914794922s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 18.576667308807373s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.526641845703125s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.37132000923157s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.065473318099976s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.127880334854126s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.15173673629760742s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.16686487197875977s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.1494901180267334s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.1652941703796387s
License | MR license check for Bio2RDF::Affymetrix took 0.3835601806640625s
License | HR license check for Bio2RDF::Affymetrix took 60.09632682800293s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.13407230377197266s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.742542743682861s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.37547898292541504s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13479256629943848s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.15422439575195312s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.3400285243988037s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.548891305923462s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.4366731643676758s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.14710330963134766s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.6522376537322998s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.19412493705749512s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.12199878692626953s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.22535109519958496s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.1270427703857422s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 108.22415089607239s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 242.2099027633667s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.5086331367492676s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15481066703796387s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12027931213378906s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.455483675003052s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8936159610748291s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6843879222869873s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.2856283187866211s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.60018539428711s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.3304495811462402s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 5.9779136180877686s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3699188232421875s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.45026612281799s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.8205223083496094s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.33325648307800293s
Security | Sign check for Bio2RDF::Affymetrix took 0.10965991020202637s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 10.823679685592651s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 60.62888526916504s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.846687316894531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 247.16310167312622s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1670.2794289588928s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 1.3007900714874268s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006325244903564453s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.874011278152466s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2765963077545166s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 45.95924234390259s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.55351114273071s
Versatility | Languages check for Bio2RDF::Biomodels took 60.24898362159729s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2675178050994873s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.16583704948425293s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.24401044845581055s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.2756686210632324s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.3100621700286865s
License | MR license check for Bio2RDF::Biomodels took 0.4074242115020752s
License | HR license check for Bio2RDF::Biomodels took 60.23915457725525s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2747344970703125s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.481769323348999s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5810439586639404s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2694261074066162s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.2534053325653076s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.3349270820617676s
Performance | Throughput check for Bio2RDF::Biomodels took 11.657705783843994s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.6244585514068604s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.2501063346862793s
Interlinking | skos check for Bio2RDF::Biomodels took 0.7616260051727295s
Interlinking | skos check for Bio2RDF::Biomodels took 0.36426424980163574s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2705678939819336s
Currency | Creation date check for Bio2RDF::Biomodels took 0.3439977169036865s
Currency | Modification date check for Bio2RDF::Biomodels took 0.24486374855041504s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 108.44947242736816s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 264.8642141819s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.726825475692749s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.29354333877563477s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2698032855987549s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.328555583953857s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9069075584411621s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6693112850189209s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.2971014976501465s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.69757723808289s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.433043956756592s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.200599670410156s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3186445236206055s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.543195486068726s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7514791488647461s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4252443313598633s
Security | Sign check for Bio2RDF::Biomodels took 0.2825968265533447s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 20.196749925613403s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 3.246232509613037s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012230873107910156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 229.67966985702515s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1537.2103700637817s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 0.14498186111450195s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00033164024353027344s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 11.497176170349121s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.02291107177734375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0010900497436523438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.933906555175781e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 131.36999082565308s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.7303924560546875s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0007002353668212891s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.150566339492798s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2094225883483887s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.89245247840881s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.721420764923096s
Versatility | Languages check for Bio2RDF::Bioportal took 60.22964644432068s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2663149833679199s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.1544189453125s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.3924686908721924s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.24968194961547852s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.3108155727386475s
License | MR license check for Bio2RDF::Bioportal took 0.5391826629638672s
License | HR license check for Bio2RDF::Bioportal took 60.25363373756409s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.26256322860717773s
Understandability | Number of label check for Bio2RDF::Bioportal took 9.138892650604248s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5901632308959961s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.23331308364868164s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2770683765411377s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.45764684677124023s
Performance | Throughput check for Bio2RDF::Bioportal took 11.705005407333374s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.741255521774292s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.2557361125946045s
Interlinking | skos check for Bio2RDF::Bioportal took 0.6235263347625732s
Interlinking | skos check for Bio2RDF::Bioportal took 0.34363293647766113s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2603738307952881s
Currency | Creation date check for Bio2RDF::Bioportal took 0.36919331550598145s
Currency | Modification date check for Bio2RDF::Bioportal took 0.2615511417388916s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 108.16305017471313s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 222.36317801475525s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.6224243640899658s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2818729877471924s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.284329891204834s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.4583563804626465s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8896126747131348s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6842141151428223s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.43684864044189453s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.03402996063232s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.493135929107666s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.506847620010376s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3240265846252441s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.56850337982178s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7534210681915283s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.45516204833984375s
Security | Sign check for Bio2RDF::Bioportal took 0.2680633068084717s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 23.77204704284668s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.7967545986175537s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.021398544311523438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00045371055603027344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 228.6347577571869s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1554.7631821632385s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.14163541793823242s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.00038433074951171875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 1.2658026218414307s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.022515058517456055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0008666515350341797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 8.511543273925781e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-chembl took 25.26002526283264s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.48674821853637695s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006618499755859375s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.951794385910034s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2666256427764893s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 45.51823163032532s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 42.58111095428467s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.251665115356445s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.26521825790405273s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.14446616172790527s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.24762439727783203s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.2471163272857666s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.550604820251465s
License | MR license check for Bio2RDF::Clinicaltrials took 0.36868739128112793s
License | HR license check for Bio2RDF::Clinicaltrials took 60.26951479911804s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.25788307189941406s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 8.740047693252563s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5797874927520752s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.25916457176208496s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.26682496070861816s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.3812520503997803s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.446709871292114s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.6041817665100098s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.27477169036865234s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.6014864444732666s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.33425378799438477s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2569739818572998s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.3694005012512207s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.2518017292022705s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 108.64288854598999s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 211.2578206062317s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.6296854019165039s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.3174717426300049s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.258176326751709s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.513264894485474s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8875408172607422s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6936049461364746s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.361055850982666s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 64.97135925292969s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.452169895172119s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.676503419876099s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3266127109527588s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.587045669555664s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7825746536254883s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.406644344329834s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.26135683059692383s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 17.98607349395752s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.3724939823150635s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 197.05294489860535s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1423.5639288425446s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.49968934059143066s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0003638267517089844s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.819229125976562s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2902934551239014s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.25453734397888s
Interoperability | New terms check for Bio2RDF::Ctd took 41.534510374069214s
Versatility | Languages check for Bio2RDF::Ctd took 60.24899458885193s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2864859104156494s
Security | Check HTTPS for Bio2RDF::Ctd took 0.17390131950378418s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.3055703639984131s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.2762458324432373s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.429100275039673s
License | MR license check for Bio2RDF::Ctd took 0.26538705825805664s
License | HR license check for Bio2RDF::Ctd took 60.245805501937866s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.25063490867614746s
Understandability | Number of label check for Bio2RDF::Ctd took 8.965206861495972s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6046686172485352s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.26462745666503906s
Verifiability | Authors check for Bio2RDF::Ctd took 0.26716136932373047s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.358734130859375s
Performance | Throughput check for Bio2RDF::Ctd took 11.066399574279785s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.5984370708465576s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.2808971405029297s
Interlinking | skos check for Bio2RDF::Ctd took 0.5592513084411621s
Interlinking | skos check for Bio2RDF::Ctd took 0.36155271530151367s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2593040466308594s
Currency | Creation date check for Bio2RDF::Ctd took 0.36630892753601074s
Currency | Modification date check for Bio2RDF::Ctd took 0.24720144271850586s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 108.45314645767212s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 174.43113732337952s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4547450542449951s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2634468078613281s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.252347469329834s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.75739049911499s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8982639312744141s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6769595146179199s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.24619603157043457s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.17193913459778s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.4099693298339844s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.563760757446289s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3497612476348877s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.589643239974976s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7546544075012207s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4272489547729492s
Security | Sign check for Bio2RDF::Ctd took 0.250349760055542s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 23.757731199264526s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 3.027888536453247s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.022228717803955078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0010826587677001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 8.940696716308594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 223.90512442588806s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-ctd took 1435.1990594863892s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 2.0879464149475098s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02852797508239746s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.001337289810180664s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 6.961822509765625e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-dataset took 4.629657983779907s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.4818873405456543s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0007216930389404297s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.37801957130432s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2848334312438965s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 45.20606827735901s
Interoperability | New terms check for Bio2RDF::Dbsnp took 43.25146508216858s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.24471044540405s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.27526044845581055s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.14883875846862793s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.25872039794921875s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.25818347930908203s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.1774649620056152s
License | MR license check for Bio2RDF::Dbsnp took 0.2468264102935791s
License | HR license check for Bio2RDF::Dbsnp took 60.23239207267761s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2567873001098633s
Understandability | Number of label check for Bio2RDF::Dbsnp took 8.997128009796143s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5781724452972412s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.24899721145629883s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2766118049621582s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.3655259609222412s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.97179651260376s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.7769718170166016s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.2898716926574707s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.6729674339294434s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.4016764163970947s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.24164342880249023s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.3686075210571289s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.26039576530456543s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 106.54269194602966s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 172.42306423187256s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4273076057434082s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2701239585876465s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.28367090225219727s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.648334503173828s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.9058704376220703s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.7036676406860352s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.31664061546325684s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.08862519264221s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 3.492816925048828s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.4695143699646s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3438785076141357s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.57547378540039s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7630043029785156s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.43766331672668457s
Security | Sign check for Bio2RDF::Dbsnp took 0.2767763137817383s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 25.082151651382446s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 17.40573740005493s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.03257322311401367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0012378692626953125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 172.83991622924805s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1384.5014057159424s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.5771770477294922s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0003991127014160156s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 19.29069757461548s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2460594177246094s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 46.05768394470215s
Interoperability | New terms check for Bio2RDF::Drugbank took 43.13481831550598s
Versatility | Languages check for Bio2RDF::Drugbank took 60.261985540390015s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2673835754394531s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.14928770065307617s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.26240968704223633s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.26177549362182617s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.5999579429626465s
License | MR license check for Bio2RDF::Drugbank took 0.4728372097015381s
License | HR license check for Bio2RDF::Drugbank took 60.240928649902344s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.24690890312194824s
Understandability | Number of label check for Bio2RDF::Drugbank took 8.93850326538086s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5720362663269043s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.258573055267334s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2565591335296631s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.3455193042755127s
Performance | Throughput check for Bio2RDF::Drugbank took 11.145249366760254s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.26263904571533203s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.25458455085754395s
Interlinking | skos check for Bio2RDF::Drugbank took 0.6414718627929688s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3538341522216797s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2449347972869873s
Currency | Creation date check for Bio2RDF::Drugbank took 0.35082077980041504s
Currency | Modification date check for Bio2RDF::Drugbank took 0.2601490020751953s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 108.36128401756287s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 184.06433081626892s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.7622768878936768s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2582516670227051s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.23034071922302246s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.591497182846069s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.9044759273529053s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.671128511428833s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.2684783935546875s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.10278749465942s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4604268074035645s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.133789777755737s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.381497859954834s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.621952533721924s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7896718978881836s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.4419982433319092s
Security | Sign check for Bio2RDF::Drugbank took 0.25675368309020996s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 22.738121271133423s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.2705528736114502s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.0001125335693359375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 162.2602982521057s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1484.3397176265717s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.5740268230438232s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006477832794189453s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.765275716781616s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.253293514251709s
Amount of data | Number of triples check for Bio2RDF::Genage took 45.77229690551758s
Interoperability | New terms check for Bio2RDF::Genage took 41.83037829399109s
Versatility | Languages check for Bio2RDF::Genage took 60.24730062484741s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2700808048248291s
Security | Check HTTPS for Bio2RDF::Genage took 0.15294885635375977s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.2549300193786621s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.26432180404663086s
Availability | RDF dump link check for Bio2RDF::Genage took 2.0917694568634033s
License | MR license check for Bio2RDF::Genage took 0.3717224597930908s
License | HR license check for Bio2RDF::Genage took 60.23766207695007s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2650423049926758s
Understandability | Number of label check for Bio2RDF::Genage took 9.706648349761963s
Understandability | URI regex check for Bio2RDF::Genage took 0.6021738052368164s
Understandability | Vocabs check for Bio2RDF::Genage took 0.26683807373046875s
Verifiability | Authors check for Bio2RDF::Genage took 0.2769625186920166s
Verifiability | Publishers check for Bio2RDF::Genage took 0.3551967144012451s
Performance | Throughput check for Bio2RDF::Genage took 11.414555788040161s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.6353743076324463s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.2578239440917969s
Interlinking | skos check for Bio2RDF::Genage took 0.6773757934570312s
Interlinking | skos check for Bio2RDF::Genage took 0.3477938175201416s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2680854797363281s
Currency | Creation date check for Bio2RDF::Genage took 0.36969614028930664s
Currency | Modification date check for Bio2RDF::Genage took 0.2527658939361572s
Rep.Conc. | URIs length for Bio2RDF::Genage took 108.9156756401062s
Interoperability | New vocabularies check for Bio2RDF::Genage took 151.580650806427s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.45716094970703125s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.27439165115356445s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.27278637886047363s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.258396863937378s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8961877822875977s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6766097545623779s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.45110511779785156s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 64.92548203468323s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.862762212753296s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.65900444984436s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3086421489715576s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.56979179382324s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7636129856109619s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.40969395637512207s
Security | Sign check for Bio2RDF::Genage took 0.26108813285827637s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 17.141764163970947s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 35.18858218193054s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.021216869354248047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0008463859558105469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.723403930664062e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 80.56693482398987s
Believability | Calculation of trust value for Bio2RDF::Genage took 3.337860107421875e-05s
INFO | --- Analysis for bio2rdf-genage took 1416.6301712989807s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 0.18192195892333984s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 2.456990957260132s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.021146059036254883s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.651878356933594e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-genbank took 272.5166654586792s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.6621537208557129s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0005791187286376953s
Extra | Recovery of all triples for Bio2RDF::Gendr took 19.190799474716187s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.243828296661377s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.30872082710266s
Interoperability | New terms check for Bio2RDF::Gendr took 41.844552516937256s
Versatility | Languages check for Bio2RDF::Gendr took 60.234636545181274s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2695739269256592s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1591506004333496s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.25403857231140137s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.25698184967041016s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.310485363006592s
License | MR license check for Bio2RDF::Gendr took 0.4982163906097412s
License | HR license check for Bio2RDF::Gendr took 60.25155711174011s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2564091682434082s
Understandability | Number of label check for Bio2RDF::Gendr took 9.228431224822998s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6141059398651123s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.25421738624572754s
Verifiability | Authors check for Bio2RDF::Gendr took 0.26299524307250977s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.37351274490356445s
Performance | Throughput check for Bio2RDF::Gendr took 10.755917072296143s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.6437408924102783s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.24887752532958984s
Interlinking | skos check for Bio2RDF::Gendr took 0.7204394340515137s
Interlinking | skos check for Bio2RDF::Gendr took 0.3402543067932129s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2514157295227051s
Currency | Creation date check for Bio2RDF::Gendr took 0.36066317558288574s
Currency | Modification date check for Bio2RDF::Gendr took 0.24142885208129883s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.00642514228821s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 97.41345500946045s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.42290472984313965s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.29422903060913086s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2538297176361084s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.339283227920532s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8886017799377441s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6749873161315918s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.4072761535644531s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.15916919708252s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.471008777618408s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.111423492431641s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3265461921691895s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.61104226112366s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7820403575897217s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.6500821113586426s
Security | Sign check for Bio2RDF::Gendr took 0.24599003791809082s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 14.48060941696167s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.9447758197784424s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02123117446899414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0009808540344238281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 7.367134094238281e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 73.22409081459045s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-gendr took 1250.8511271476746s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4990665912628174s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0005974769592285156s
Extra | Recovery of all triples for Bio2RDF::Goa took 18.6226646900177s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2500700950622559s
Amount of data | Number of triples check for Bio2RDF::Goa took 44.91869831085205s
Interoperability | New terms check for Bio2RDF::Goa took 40.24531865119934s
Versatility | Languages check for Bio2RDF::Goa took 60.26127648353577s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.26233339309692383s
Security | Check HTTPS for Bio2RDF::Goa took 0.1574399471282959s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.2681851387023926s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.23526930809020996s
Availability | RDF dump link check for Bio2RDF::Goa took 2.342137575149536s
License | MR license check for Bio2RDF::Goa took 0.5101664066314697s
License | HR license check for Bio2RDF::Goa took 60.26247501373291s
Amount of data | Number of property check for Bio2RDF::Goa took 0.25171923637390137s
Understandability | Number of label check for Bio2RDF::Goa took 10.001802921295166s
Understandability | URI regex check for Bio2RDF::Goa took 0.5806078910827637s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2684948444366455s
Verifiability | Authors check for Bio2RDF::Goa took 0.2703845500946045s
Verifiability | Publishers check for Bio2RDF::Goa took 0.38776135444641113s
Performance | Throughput check for Bio2RDF::Goa took 11.094383001327515s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.6167318820953369s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.25835299491882324s
Interlinking | skos check for Bio2RDF::Goa took 0.5740823745727539s
Interlinking | skos check for Bio2RDF::Goa took 0.34406232833862305s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2471480369567871s
Currency | Creation date check for Bio2RDF::Goa took 0.38179731369018555s
Currency | Modification date check for Bio2RDF::Goa took 0.2748892307281494s
Rep.Conc. | URIs length for Bio2RDF::Goa took 108.91265320777893s
Interoperability | New vocabularies check for Bio2RDF::Goa took 110.51974296569824s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.40090155601501465s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2916445732116699s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.28716206550598145s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 6.591620683670044s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8965945243835449s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6634604930877686s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.2569620609283447s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.23014307022095s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.549699306488037s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.422718286514282s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3187079429626465s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.72243881225586s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7614545822143555s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.48167920112609863s
Security | Sign check for Bio2RDF::Goa took 0.259505033493042s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 9.951794624328613s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 1.1659808158874512s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.365776062011719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 88.8845956325531s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-goa took 1219.2583503723145s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.6632404327392578s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0007390975952148438s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 18.93396496772766s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2605769634246826s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 45.475494384765625s
Interoperability | New terms check for Bio2RDF::Hgnc took 41.646787881851196s
Versatility | Languages check for Bio2RDF::Hgnc took 60.251564025878906s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.46227478981018066s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.14344239234924316s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.49670958518981934s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.2593505382537842s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.260998010635376s
License | MR license check for Bio2RDF::Hgnc took 0.4889404773712158s
License | HR license check for Bio2RDF::Hgnc took 60.23904776573181s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2607457637786865s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.027320861816406s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.6176700592041016s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.24359965324401855s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.25218677520751953s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.43761134147644043s
Performance | Throughput check for Bio2RDF::Hgnc took 10.586966753005981s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.2616710662841797s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.2523229122161865s
Interlinking | skos check for Bio2RDF::Hgnc took 0.7562665939331055s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3705885410308838s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2745335102081299s
Currency | Creation date check for Bio2RDF::Hgnc took 0.3497767448425293s
Currency | Modification date check for Bio2RDF::Hgnc took 0.23514413833618164s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.53834319114685s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 91.85997486114502s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.7999463081359863s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.28808069229125977s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.27375006675720215s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 6.945403575897217s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.901252269744873s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.683659553527832s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.3898487091064453s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.01073503494263s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.4390270709991455s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.006997585296631s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3113021850585938s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.53026056289673s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7700083255767822s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4632995128631592s
Security | Sign check for Bio2RDF::Hgnc took 0.2742481231689453s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 12.304187774658203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 60.52985239028931s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.025666475296020508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 0.00012063980102539062s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0016703605651855469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00019979476928710938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 115.56042647361755s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1755.579615354538s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.524836540222168s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0002994537353515625s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.179702758789062s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2332983016967773s
Amount of data | Number of triples check for Bio2RDF::Homologene took 44.43825817108154s
Interoperability | New terms check for Bio2RDF::Homologene took 41.20367240905762s
Versatility | Languages check for Bio2RDF::Homologene took 60.23296141624451s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2718698978424072s
Security | Check HTTPS for Bio2RDF::Homologene took 0.1564188003540039s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.3482961654663086s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.24117088317871094s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.3380913734436035s
License | MR license check for Bio2RDF::Homologene took 0.5019171237945557s
License | HR license check for Bio2RDF::Homologene took 60.243165493011475s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.2626354694366455s
Understandability | Number of label check for Bio2RDF::Homologene took 10.306024551391602s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5812876224517822s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.2568359375s
Verifiability | Authors check for Bio2RDF::Homologene took 0.26743602752685547s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.4491138458251953s
Performance | Throughput check for Bio2RDF::Homologene took 11.051505327224731s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.7145445346832275s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.2614712715148926s
Interlinking | skos check for Bio2RDF::Homologene took 0.7983126640319824s
Interlinking | skos check for Bio2RDF::Homologene took 0.35243749618530273s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.2785968780517578s
Currency | Creation date check for Bio2RDF::Homologene took 0.357313871383667s
Currency | Modification date check for Bio2RDF::Homologene took 0.2511003017425537s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 109.87097668647766s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 290.91738653182983s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.8236010074615479s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.27629947662353516s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.2502450942993164s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.24343204498291s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8905930519104004s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6706986427307129s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.40668702125549316s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 64.95204329490662s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4560844898223877s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 5.9464006423950195s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3219025135040283s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.56963634490967s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7616851329803467s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4401254653930664s
Security | Sign check for Bio2RDF::Homologene took 0.265700101852417s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 10.912611722946167s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.3855745792388916s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02088451385498047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 264.9560399055481s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-homologene took 1702.3132479190826s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 9.298324584960938e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 60.27668118476868s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.027812719345092773s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0013992786407470703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 5.555152893066406e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 3.314018249511719e-05s
INFO | --- Analysis for bio2rdf-inoh took 181.48754382133484s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.9386036396026611s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0007436275482177734s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.92385220527649s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2390246391296387s
Amount of data | Number of triples check for Bio2RDF::Interpro took 45.461875915527344s
Interoperability | New terms check for Bio2RDF::Interpro took 42.983336210250854s
Versatility | Languages check for Bio2RDF::Interpro took 60.23966670036316s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.4761338233947754s
Security | Check HTTPS for Bio2RDF::Interpro took 0.15739154815673828s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.5722239017486572s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.24834012985229492s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.299670934677124s
License | MR license check for Bio2RDF::Interpro took 0.4919126033782959s
License | HR license check for Bio2RDF::Interpro took 60.25918698310852s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2613484859466553s
Understandability | Number of label check for Bio2RDF::Interpro took 9.53016996383667s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5762567520141602s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.24531269073486328s
Verifiability | Authors check for Bio2RDF::Interpro took 0.26531195640563965s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.4301168918609619s
Performance | Throughput check for Bio2RDF::Interpro took 11.646977663040161s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.2496635913848877s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.2630343437194824s
Interlinking | skos check for Bio2RDF::Interpro took 0.9826200008392334s
Interlinking | skos check for Bio2RDF::Interpro took 0.34602832794189453s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.26707983016967773s
Currency | Creation date check for Bio2RDF::Interpro took 0.3670837879180908s
Currency | Modification date check for Bio2RDF::Interpro took 0.2564706802368164s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 108.85326743125916s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 247.13615655899048s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 1.1815180778503418s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2725536823272705s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.27640652656555176s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.118927240371704s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8943915367126465s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6797511577606201s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.41426515579223633s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.40331864356995s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.4640233516693115s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.111988067626953s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3266985416412354s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.629729986190796s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7790591716766357s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4472205638885498s
Security | Sign check for Bio2RDF::Interpro took 0.28331780433654785s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 10.086076021194458s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 1.0505142211914062s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02102518081665039s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010919570922851562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 240.0567021369934s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-interpro took 2038.5769345760345s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.1387462615966797s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.8728408813476562s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 8.797645568847656e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-iproclass took 20.705885648727417s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4733705520629883s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0007138252258300781s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.717922687530518s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2867693901062012s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 46.09120440483093s
Interoperability | New terms check for Bio2RDF::Irefindex took 42.420822858810425s
Versatility | Languages check for Bio2RDF::Irefindex took 60.23481488227844s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.26313161849975586s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15944194793701172s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.372896671295166s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.256880521774292s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.2970058917999268s
License | MR license check for Bio2RDF::Irefindex took 0.4777522087097168s
License | HR license check for Bio2RDF::Irefindex took 60.259517431259155s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.25997090339660645s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.84727430343628s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5713202953338623s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.23086905479431152s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.243818998336792s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.3431966304779053s
Performance | Throughput check for Bio2RDF::Irefindex took 11.10126519203186s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6019349098205566s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.2632484436035156s
Interlinking | skos check for Bio2RDF::Irefindex took 1.009795904159546s
Interlinking | skos check for Bio2RDF::Irefindex took 0.39693570137023926s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.23141241073608398s
Currency | Creation date check for Bio2RDF::Irefindex took 0.36754918098449707s
Currency | Modification date check for Bio2RDF::Irefindex took 0.2565011978149414s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 107.99592185020447s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 282.720299243927s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.6227843761444092s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2724494934082031s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.264568567276001s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.672548770904541s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8885576725006104s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6890294551849365s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.40435194969177246s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 64.87956762313843s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.45242977142334s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.1150431632995605s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.365922212600708s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.62657427787781s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7846858501434326s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4347066879272461s
Security | Sign check for Bio2RDF::Irefindex took 0.24827170372009277s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 25.732101440429688s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.8369932174682617s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02221226692199707s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0009829998016357422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 9.5367431640625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 264.7611565589905s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1573.0544037818909s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 0.473588228225708s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0006127357482910156s
Extra | Recovery of all triples for Bio2RDF::KEGG took 18.780193567276s
Performance | Total latancy measurement for Bio2RDF::KEGG took 1.237588882446289s
Amount of data | Number of triples check for Bio2RDF::KEGG took 45.05867648124695s
Interoperability | New terms check for Bio2RDF::KEGG took 43.47555351257324s
Versatility | Languages check for Bio2RDF::KEGG took 60.2463002204895s
Interpretability | Number of blank nodes check for Bio2RDF::KEGG took 0.2805771827697754s
Security | Check HTTPS for Bio2RDF::KEGG took 0.16202569007873535s
Interpretability | RDF structures check for Bio2RDF::KEGG took 0.563368558883667s
Versatility | Serialization formats check for Bio2RDF::KEGG took 0.2647585868835449s
Availability | RDF dump link check for Bio2RDF::KEGG took 2.1780290603637695s
License | MR license check for Bio2RDF::KEGG took 0.6698658466339111s
License | HR license check for Bio2RDF::KEGG took 60.239930152893066s
Amount of data | Number of property check for Bio2RDF::KEGG took 0.2580564022064209s
Understandability | Number of label check for Bio2RDF::KEGG took 10.200614929199219s
Understandability | URI regex check for Bio2RDF::KEGG took 0.5409660339355469s
Understandability | Vocabs check for Bio2RDF::KEGG took 0.24811887741088867s
Verifiability | Authors check for Bio2RDF::KEGG took 0.24981212615966797s
Verifiability | Publishers check for Bio2RDF::KEGG took 0.43918371200561523s
Performance | Throughput check for Bio2RDF::KEGG took 11.39387321472168s
Verifiability | Contribs. check for Bio2RDF::KEGG took 0.6289207935333252s
Interlinking | sameAs chians check for Bio2RDF::KEGG took 0.27344536781311035s
Interlinking | skos check for Bio2RDF::KEGG took 0.7459113597869873s
Interlinking | skos check for Bio2RDF::KEGG took 0.33702874183654785s
Timeliness | dataset update frequency check for Bio2RDF::KEGG took 0.25014352798461914s
Currency | Creation date check for Bio2RDF::KEGG took 0.3513305187225342s
Currency | Modification date check for Bio2RDF::KEGG took 0.2485065460205078s
Rep.Conc. | URIs length for Bio2RDF::KEGG took 107.69159960746765s
Interoperability | New vocabularies check for Bio2RDF::KEGG took 243.78615832328796s
Consistency | Deprecated classes/propertiers check for Bio2RDF::KEGG took 0.7192847728729248s
Accuracy | Check Functional Property for Bio2RDF::KEGG took 0.28394651412963867s
Accuracy | Check Inverse Functional Property for Bio2RDF::KEGG took 0.2530686855316162s
Accuracy | Check Empty annotation labels for Bio2RDF::KEGG took 6.695866346359253s
Accuracy | Check White space in annotation for Bio2RDF::KEGG took 0.8928687572479248s
Accuracy | Check Datatype consistency for Bio2RDF::KEGG took 0.6670536994934082s
Consistency | Disjoint class check for Bio2RDF::KEGG took 0.3881096839904785s
Consistency | Check Misplaced properties for Bio2RDF::KEGG took 65.02389526367188s
Consistency | Misplaced classes for Bio2RDF::KEGG took 2.4663491249084473s
Consistency | Check Ontology hijacking for Bio2RDF::KEGG took 6.493285894393921s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::KEGG took 1.4376318454742432s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::KEGG took 61.58170199394226s
Conciseness | Check Extensional conciseness for Bio2RDF::KEGG took 0.7561421394348145s
Conciseness | Check Intensional conciseness for Bio2RDF::KEGG took 0.40393877029418945s
Security | Sign check for Bio2RDF::KEGG took 0.2783353328704834s
Availability | Check URIs Dereferenciability for Bio2RDF::KEGG took 11.280450105667114s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.7108619213104248s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::KEGG took 249.48687553405762s
Believability | Calculation of trust value for Bio2RDF::KEGG took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-kegg took 1495.020753145218s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 0.1332411766052246s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 3.269770622253418s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02250194549560547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.3855438232421875e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 13.331032276153564s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13750934600830078s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 1.5982651710510254s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.0225374698638916s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 12.22751760482788s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.4661407470703125s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005943775177001953s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.800270080566406s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.258425235748291s
Amount of data | Number of triples check for Bio2RDF::Lsr took 45.169466972351074s
Interoperability | New terms check for Bio2RDF::Lsr took 42.76661944389343s
Versatility | Languages check for Bio2RDF::Lsr took 60.2480103969574s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2656896114349365s
Security | Check HTTPS for Bio2RDF::Lsr took 0.16604328155517578s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.5484983921051025s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.2439897060394287s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.19301176071167s
License | MR license check for Bio2RDF::Lsr took 0.4798905849456787s
License | HR license check for Bio2RDF::Lsr took 60.258567094802856s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2601194381713867s
Understandability | Number of label check for Bio2RDF::Lsr took 9.555651187896729s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6007685661315918s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.24552392959594727s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2647120952606201s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.33924365043640137s
Performance | Throughput check for Bio2RDF::Lsr took 11.350468397140503s
Verifiability | Contribs. check for Bio2RDF::Lsr took 2.0285398960113525s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.2578139305114746s
Interlinking | skos check for Bio2RDF::Lsr took 0.7095167636871338s
Interlinking | skos check for Bio2RDF::Lsr took 0.36345577239990234s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.23372936248779297s
Currency | Creation date check for Bio2RDF::Lsr took 0.36329078674316406s
Currency | Modification date check for Bio2RDF::Lsr took 0.26211977005004883s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 107.86696910858154s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 231.576726436615s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.6566169261932373s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2604084014892578s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.28680944442749023s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.865650415420532s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.916008710861206s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.7391095161437988s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.39582061767578125s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 64.78603720664978s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.475027561187744s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.18324613571167s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3325536251068115s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.58415341377258s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7773435115814209s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4345521926879883s
Security | Sign check for Bio2RDF::Lsr took 0.28415679931640625s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 25.814706563949585s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 179.8537299633026s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.021121978759765625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 259.8645496368408s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-lsr took 1757.513989686966s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.7200744152069092s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.00042438507080078125s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.147666931152344s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2504281997680664s
Amount of data | Number of triples check for Bio2RDF::Mesh took 44.46815776824951s
Interoperability | New terms check for Bio2RDF::Mesh took 42.32274651527405s
Versatility | Languages check for Bio2RDF::Mesh took 60.237247467041016s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.27605605125427246s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15518546104431152s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.5217714309692383s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.2664470672607422s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.285175323486328s
License | MR license check for Bio2RDF::Mesh took 0.48773717880249023s
License | HR license check for Bio2RDF::Mesh took 60.26537728309631s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.45186662673950195s
Understandability | Number of label check for Bio2RDF::Mesh took 10.085166931152344s
Understandability | URI regex check for Bio2RDF::Mesh took 0.607419490814209s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2501354217529297s
Verifiability | Authors check for Bio2RDF::Mesh took 0.26106834411621094s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.4216785430908203s
Performance | Throughput check for Bio2RDF::Mesh took 11.088646650314331s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.24261760711669922s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.2555558681488037s
Interlinking | skos check for Bio2RDF::Mesh took 0.8009676933288574s
Interlinking | skos check for Bio2RDF::Mesh took 0.35772204399108887s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.26396727561950684s
Currency | Creation date check for Bio2RDF::Mesh took 0.33843398094177246s
Currency | Modification date check for Bio2RDF::Mesh took 0.24773883819580078s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 108.4758632183075s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 211.40618062019348s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.7675907611846924s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2929060459136963s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2762441635131836s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.085697650909424s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8936841487884521s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6763217449188232s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.3925914764404297s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.23597145080566s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.4703478813171387s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.048314571380615s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3101806640625s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.5721652507782s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7523276805877686s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.40436601638793945s
Security | Sign check for Bio2RDF::Mesh took 0.2773604393005371s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 25.87969732284546s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.9493107795715332s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.0208437442779541s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 0.00011801719665527344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 117.17073702812195s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-mesh took 1596.1352455615997s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.48739051818847656s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006091594696044922s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.061286687850952s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2639353275299072s
Amount of data | Number of triples check for Bio2RDF::Mgi took 44.31945824623108s
Interoperability | New terms check for Bio2RDF::Mgi took 42.604573488235474s
Versatility | Languages check for Bio2RDF::Mgi took 60.250117778778076s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.28318142890930176s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15601825714111328s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.24586081504821777s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.25581836700439453s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.344611883163452s
License | MR license check for Bio2RDF::Mgi took 0.45480775833129883s
License | HR license check for Bio2RDF::Mgi took 60.23844528198242s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.2554910182952881s
Understandability | Number of label check for Bio2RDF::Mgi took 9.822028875350952s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5778472423553467s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2541794776916504s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2564084529876709s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.45211315155029297s
Performance | Throughput check for Bio2RDF::Mgi took 10.92897891998291s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.765742301940918s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.2569925785064697s
Interlinking | skos check for Bio2RDF::Mgi took 0.793846845626831s
Interlinking | skos check for Bio2RDF::Mgi took 0.3402407169342041s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2560133934020996s
Currency | Creation date check for Bio2RDF::Mgi took 0.34933996200561523s
Currency | Modification date check for Bio2RDF::Mgi took 0.24363923072814941s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 109.24251961708069s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 146.73739528656006s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.40606117248535156s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2319934368133545s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.27516913414001465s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.120506763458252s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8942058086395264s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6842689514160156s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.41579437255859375s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.1086757183075s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.653251886367798s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.032709121704102s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.310978889465332s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.57618021965027s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7728962898254395s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.4209635257720947s
Security | Sign check for Bio2RDF::Mgi took 0.27019500732421875s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 18.586036920547485s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.7550065517425537s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02094292640686035s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.00011110305786132812s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 168.77293753623962s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-mgi took 1336.9057619571686s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.4908769130706787s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006268024444580078s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.53170371055603s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.3119423389434814s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 46.109004735946655s
Interoperability | New terms check for Bio2RDF::Ncbigene took 42.4503116607666s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.277215242385864s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2640080451965332s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1596207618713379s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.37499237060546875s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.25928497314453125s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.424497127532959s
License | MR license check for Bio2RDF::Ncbigene took 0.27676916122436523s
License | HR license check for Bio2RDF::Ncbigene took 60.23128914833069s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.25039029121398926s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.21713638305664s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5921883583068848s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.24919819831848145s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.27017903327941895s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.36847996711730957s
Performance | Throughput check for Bio2RDF::Ncbigene took 10.389440298080444s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.6495697498321533s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.27464914321899414s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.5121562480926514s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3415951728820801s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2548351287841797s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.38071656227111816s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.2505941390991211s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 107.79826021194458s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 131.6215522289276s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.44095468521118164s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2771718502044678s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.27887654304504395s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.099818706512451s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8952393531799316s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.671320915222168s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.5018162727355957s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.34462428092957s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.7830982208251953s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.156411409378052s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3123290538787842s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.60142159461975s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7737855911254883s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.4064772129058838s
Security | Sign check for Bio2RDF::Ncbigene took 0.25434327125549316s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 23.148926496505737s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 3.8615965843200684s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011539459228515625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 157.3939881324768s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.621246337890625e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1324.5831997394562s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.48728084564208984s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.00067138671875s
Extra | Recovery of all triples for Bio2RDF::Ndc took 19.246306896209717s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2860889434814453s
Amount of data | Number of triples check for Bio2RDF::Ndc took 44.60147213935852s
Interoperability | New terms check for Bio2RDF::Ndc took 42.49902272224426s
Versatility | Languages check for Bio2RDF::Ndc took 60.25938820838928s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2910754680633545s
Security | Check HTTPS for Bio2RDF::Ndc took 0.16052913665771484s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.634286642074585s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.2579045295715332s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.2077486515045166s
License | MR license check for Bio2RDF::Ndc took 0.6208944320678711s
License | HR license check for Bio2RDF::Ndc took 60.26181626319885s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2614889144897461s
Understandability | Number of label check for Bio2RDF::Ndc took 9.71778655052185s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5804531574249268s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2587392330169678s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2562694549560547s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.36859560012817383s
Performance | Throughput check for Bio2RDF::Ndc took 11.284284114837646s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.6429188251495361s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.26271867752075195s
Interlinking | skos check for Bio2RDF::Ndc took 0.5913090705871582s
Interlinking | skos check for Bio2RDF::Ndc took 0.353039026260376s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.24541139602661133s
Currency | Creation date check for Bio2RDF::Ndc took 0.3734598159790039s
Currency | Modification date check for Bio2RDF::Ndc took 0.24998974800109863s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 108.74262595176697s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 110.29509425163269s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4082517623901367s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2826220989227295s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2648782730102539s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 6.585789680480957s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8929011821746826s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6762571334838867s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.40169286727905273s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.08161997795105s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.471339225769043s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.419915676116943s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.324732780456543s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.80991744995117s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7816765308380127s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.4436159133911133s
Security | Sign check for Bio2RDF::Ndc took 0.2641749382019043s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 17.32512664794922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 32.03181028366089s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.021180152893066406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 77.81638360023499s
Believability | Calculation of trust value for Bio2RDF::Ndc took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-ndc took 1233.2929830551147s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 0.13478374481201172s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00031280517578125s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.48294878005981445s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.021470069885253906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-netpath took 124.29589939117432s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.1743309497833252s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.5770790576934814s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020922422409057617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-nextprot took 4.553629159927368s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.5228562355041504s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0005753040313720703s
Extra | Recovery of all triples for Bio2RDF::Omim took 17.915201425552368s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2715575695037842s
Amount of data | Number of triples check for Bio2RDF::Omim took 46.01033020019531s
Interoperability | New terms check for Bio2RDF::Omim took 42.53975200653076s
Versatility | Languages check for Bio2RDF::Omim took 60.2290780544281s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2809743881225586s
Security | Check HTTPS for Bio2RDF::Omim took 0.14501452445983887s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.9257709980010986s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.262650728225708s
Availability | RDF dump link check for Bio2RDF::Omim took 2.3478176593780518s
License | MR license check for Bio2RDF::Omim took 0.2721879482269287s
License | HR license check for Bio2RDF::Omim took 60.29725742340088s
Amount of data | Number of property check for Bio2RDF::Omim took 0.26898694038391113s
Understandability | Number of label check for Bio2RDF::Omim took 10.09242844581604s
Understandability | URI regex check for Bio2RDF::Omim took 0.5995702743530273s
Understandability | Vocabs check for Bio2RDF::Omim took 0.24482989311218262s
Verifiability | Authors check for Bio2RDF::Omim took 0.28267478942871094s
Verifiability | Publishers check for Bio2RDF::Omim took 0.3381030559539795s
Performance | Throughput check for Bio2RDF::Omim took 11.111265182495117s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.6323997974395752s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.27176666259765625s
Interlinking | skos check for Bio2RDF::Omim took 0.7694358825683594s
Interlinking | skos check for Bio2RDF::Omim took 0.3448672294616699s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.24451923370361328s
Currency | Creation date check for Bio2RDF::Omim took 0.3638916015625s
Currency | Modification date check for Bio2RDF::Omim took 0.260831356048584s
Rep.Conc. | URIs length for Bio2RDF::Omim took 107.60781764984131s
Interoperability | New vocabularies check for Bio2RDF::Omim took 74.23256492614746s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4260568618774414s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.28867244720458984s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2670750617980957s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.650161266326904s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.9028842449188232s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6795945167541504s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.45433545112609863s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 64.96868753433228s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.4760477542877197s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 8.484918117523193s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3143510818481445s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.559141635894775s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7703790664672852s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.6363017559051514s
Security | Sign check for Bio2RDF::Omim took 0.26518702507019043s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 10.400871753692627s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.6983940601348877s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020935773849487305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013828277587890625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 88.8057701587677s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-omim took 1172.2721538543701s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 5.698204040527344e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.000347137451171875s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.3092927932739258s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.910064697265625e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 2.0048208236694336s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.4956800937652588s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006396770477294922s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.719780683517456s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2723791599273682s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.57726192474365s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.585421085357666s
Versatility | Languages check for Bio2RDF::Orphanet took 60.247700452804565s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.2697005271911621s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.14822936058044434s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.4479193687438965s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.25885534286499023s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.233187198638916s
License | MR license check for Bio2RDF::Orphanet took 0.39042162895202637s
License | HR license check for Bio2RDF::Orphanet took 60.24682855606079s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2855348587036133s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.182384967803955s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.6091160774230957s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2521021366119385s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.24665379524230957s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.5351459980010986s
Performance | Throughput check for Bio2RDF::Orphanet took 10.81111216545105s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.5913913249969482s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.26448583602905273s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7083806991577148s
Interlinking | skos check for Bio2RDF::Orphanet took 0.351531982421875s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2602863311767578s
Currency | Creation date check for Bio2RDF::Orphanet took 0.38452696800231934s
Currency | Modification date check for Bio2RDF::Orphanet took 0.24202370643615723s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 109.6937038898468s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 77.92565608024597s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4377870559692383s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.27919816970825195s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.27428746223449707s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.887204170227051s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9536466598510742s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.8088598251342773s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.3249399662017822s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.34919476509094s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.4473507404327393s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.370185375213623s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3037419319152832s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.55040121078491s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7686679363250732s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.657062292098999s
Security | Sign check for Bio2RDF::Orphanet took 0.2735323905944824s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 26.77081847190857s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 2.1001124382019043s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.021591663360595703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.869171142578125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 72.1553680896759s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1181.3947761058807s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.14199161529541016s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.36480140686035156s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.02229785919189453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 8.7202308177948s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.48584699630737305s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005567073822021484s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.560437202453613s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.285783290863037s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 45.473694801330566s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 41.586079120635986s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.24697661399841s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.25823068618774414s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16852235794067383s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.7512359619140625s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.26229262351989746s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.304503917694092s
License | MR license check for Bio2RDF::Pharmgkb took 0.6082141399383545s
License | HR license check for Bio2RDF::Pharmgkb took 60.24112820625305s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.25261831283569336s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.075087308883667s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5964019298553467s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.25803446769714355s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2546091079711914s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.46593666076660156s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.278224229812622s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 1.6925537586212158s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.2706489562988281s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.8585822582244873s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.34793758392333984s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.25717973709106445s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.36745166778564453s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.24674749374389648s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 109.67923069000244s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 82.64683389663696s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.39140868186950684s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.23123979568481445s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2656524181365967s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.8349175453186035s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8940458297729492s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.681736946105957s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.41861581802368164s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.49618935585022s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4663000106811523s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.549990177154541s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3048732280731201s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.55281043052673s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7709596157073975s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.7511789798736572s
Security | Sign check for Bio2RDF::Pharmgkb took 0.27969980239868164s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 24.977632761001587s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.8783419132232666s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.0217745304107666s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0009360313415527344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 8.535385131835938e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 61.43084478378296s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1181.1631801128387s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 0.13729572296142578s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 5.031886339187622s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.409385681152344e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 15.495404243469238s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 0.13873887062072754s
Availability | VoID file availability check for Bio2RDF::PID took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.32008790969848633s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pid took 4.224305629730225s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 0.13494539260864258s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.8618695735931396s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020825862884521484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-pubchem-2 took 6.554329872131348s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.49038195610046387s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006544589996337891s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 19.57450819015503s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2335281372070312s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.69355821609497s
Interoperability | New terms check for Bio2RDF::Pubmed took 43.28178691864014s
Versatility | Languages check for Bio2RDF::Pubmed took 60.24317169189453s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.277510404586792s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.16762685775756836s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.5296783447265625s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.2656576633453369s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.3164896965026855s
License | MR license check for Bio2RDF::Pubmed took 0.48315882682800293s
License | HR license check for Bio2RDF::Pubmed took 60.26349592208862s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.3102264404296875s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.055081129074097s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6185886859893799s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2640409469604492s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2712981700897217s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.39116787910461426s
Performance | Throughput check for Bio2RDF::Pubmed took 10.58011507987976s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.58990478515625s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.26752233505249023s
Interlinking | skos check for Bio2RDF::Pubmed took 0.8808150291442871s
Interlinking | skos check for Bio2RDF::Pubmed took 0.4181065559387207s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2568178176879883s
Currency | Creation date check for Bio2RDF::Pubmed took 0.3393423557281494s
Currency | Modification date check for Bio2RDF::Pubmed took 0.2498619556427002s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 108.98282742500305s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 89.69526553153992s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.7054624557495117s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.28833580017089844s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2786390781402588s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.956713914871216s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8887016773223877s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6873166561126709s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.3796679973602295s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 64.92401313781738s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.438593626022339s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.302185535430908s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.311863899230957s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.55905199050903s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.772418737411499s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.5692253112792969s
Security | Sign check for Bio2RDF::Pubmed took 0.268463134765625s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 24.223804473876953s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 1.0273447036743164s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.022137880325317383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014829635620117188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 107.39343881607056s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1323.392719745636s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 5.817413330078125e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.31213927268981934s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.022320985794067383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 9.274482727050781e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 1.811981201171875e-05s
INFO | --- Analysis for bio2rdf-reactome took 498.17349886894226s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 9.1552734375e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0003669261932373047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 11.192267656326294s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.03395867347717285s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 3.0517578125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0014426708221435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 0.00010204315185546875s
Believability | Calculation of trust value for Bio2RDF::Rhea took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-rhea took 295.30776810646057s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.30733823776245117s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 59.746739864349365s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.940696716308594e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-sabiork took 200.64627742767334s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.8950293064117432s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006017684936523438s
Extra | Recovery of all triples for Bio2RDF::Sgd took 22.39238929748535s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2393996715545654s
Amount of data | Number of triples check for Bio2RDF::Sgd took 46.77912712097168s
Interoperability | New terms check for Bio2RDF::Sgd took 41.7260799407959s
Versatility | Languages check for Bio2RDF::Sgd took 60.259440898895264s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.251049280166626s
Security | Check HTTPS for Bio2RDF::Sgd took 0.16892337799072266s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.4987335205078125s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.25124692916870117s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.3944003582000732s
License | MR license check for Bio2RDF::Sgd took 0.6388566493988037s
License | HR license check for Bio2RDF::Sgd took 60.274611473083496s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2559666633605957s
Understandability | Number of label check for Bio2RDF::Sgd took 10.299758911132812s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5987679958343506s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2535421848297119s
Verifiability | Authors check for Bio2RDF::Sgd took 0.25903820991516113s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.3719978332519531s
Performance | Throughput check for Bio2RDF::Sgd took 10.552664041519165s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.6584422588348389s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.2591736316680908s
Interlinking | skos check for Bio2RDF::Sgd took 0.7269339561462402s
Interlinking | skos check for Bio2RDF::Sgd took 0.34129858016967773s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.24832630157470703s
Currency | Creation date check for Bio2RDF::Sgd took 0.356503963470459s
Currency | Modification date check for Bio2RDF::Sgd took 0.2706761360168457s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 109.5832736492157s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 49.2564013004303s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4210495948791504s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.261946439743042s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.28531455993652344s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 7.285474538803101s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9011039733886719s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6997497081756592s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.42973923683166504s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.1932532787323s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.5247859954833984s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.426682233810425s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.30875563621521s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.557597398757935s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7716405391693115s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.6535322666168213s
Security | Sign check for Bio2RDF::Sgd took 0.2798290252685547s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 14.874263763427734s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 180.4723207950592s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.022049903869628906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00012493133544921875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 45.70520544052124s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-sgd took 1419.6248455047607s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 9.441375732421875e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 59.63118052482605s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.023216724395751953s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.647804260253906e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 66.56401801109314s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.6453812122344971s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006067752838134766s
Extra | Recovery of all triples for Bio2RDF::Sider took 19.25843572616577s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2338244915008545s
Amount of data | Number of triples check for Bio2RDF::Sider took 45.80572152137756s
Interoperability | New terms check for Bio2RDF::Sider took 42.97668766975403s
Versatility | Languages check for Bio2RDF::Sider took 60.24980688095093s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2768728733062744s
Security | Check HTTPS for Bio2RDF::Sider took 0.1563875675201416s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.2723660469055176s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.27135562896728516s
Availability | RDF dump link check for Bio2RDF::Sider took 2.352567195892334s
License | MR license check for Bio2RDF::Sider took 0.5251386165618896s
License | HR license check for Bio2RDF::Sider took 60.27386498451233s
Amount of data | Number of property check for Bio2RDF::Sider took 0.2565484046936035s
Understandability | Number of label check for Bio2RDF::Sider took 9.500645399093628s
Understandability | URI regex check for Bio2RDF::Sider took 0.5850553512573242s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2610759735107422s
Verifiability | Authors check for Bio2RDF::Sider took 0.2738368511199951s
Verifiability | Publishers check for Bio2RDF::Sider took 0.3890712261199951s
Performance | Throughput check for Bio2RDF::Sider took 10.895639896392822s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.6288135051727295s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.2633497714996338s
Interlinking | skos check for Bio2RDF::Sider took 0.8070745468139648s
Interlinking | skos check for Bio2RDF::Sider took 0.3453359603881836s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.25255751609802246s
Currency | Creation date check for Bio2RDF::Sider took 0.35704898834228516s
Currency | Modification date check for Bio2RDF::Sider took 0.2343614101409912s
Rep.Conc. | URIs length for Bio2RDF::Sider took 109.47159194946289s
Interoperability | New vocabularies check for Bio2RDF::Sider took 50.10615515708923s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.42064952850341797s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.24925732612609863s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2530488967895508s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.811354398727417s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.9346339702606201s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.7603743076324463s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.2672138214111328s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.44406509399414s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.444206714630127s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.5801849365234375s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.319031000137329s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.58313250541687s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7707767486572266s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 1.4438996315002441s
Security | Sign check for Bio2RDF::Sider took 0.2583489418029785s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 10.231282472610474s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 39.395397424697876s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.02193164825439453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 3.719329833984375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0012159347534179688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 41.24341297149658s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-sider took 1246.4169554710388s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 0.00016736984252929688s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0008223056793212891s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 59.61852836608887s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.0211484432220459s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 6.175041198730469e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 2.002716064453125e-05s
INFO | --- Analysis for bio2rdf-spike took 697.2882668972015s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 8.845329284667969e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 25.096292734146118s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.021405935287475586s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.315376281738281e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-taxon took 44.36297106742859s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 1.4304251670837402s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0007305145263671875s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.867550134658813s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.252061367034912s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 46.45131516456604s
Interoperability | New terms check for Bio2RDF::Taxonomy took 43.35208773612976s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.258363008499146s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2581672668457031s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.15891385078430176s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.6372764110565186s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.26496386528015137s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.280454158782959s
License | MR license check for Bio2RDF::Taxonomy took 0.49652624130249023s
License | HR license check for Bio2RDF::Taxonomy took 60.261799812316895s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.26065683364868164s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.699771404266357s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5840444564819336s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2557644844055176s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.25618553161621094s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.36568760871887207s
Performance | Throughput check for Bio2RDF::Taxonomy took 10.335737466812134s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 1.079857349395752s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.25651121139526367s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.5687284469604492s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.35674047470092773s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2368912696838379s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.36287569999694824s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.2929816246032715s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 110.59462475776672s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 36.67432975769043s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4531257152557373s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2436976432800293s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.28271007537841797s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.57749605178833s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.89890456199646s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6975245475769043s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.36962294578552246s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.33826041221619s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.4485363960266113s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.457533836364746s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3088252544403076s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.66303563117981s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7838687896728516s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.44301748275756836s
Security | Sign check for Bio2RDF::Taxonomy took 1.423076868057251s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.874872207641602s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.6479315757751465s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.021167755126953125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010728836059570312s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 50.67856812477112s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1109.661033153534s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.14302706718444824s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.582205057144165s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 19.30214810371399s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.479705810546875s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006754398345947266s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.249403476715088s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.236847162246704s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.575961112976074s
Interoperability | New terms check for Bio2RDF::Wormbase took 42.1781907081604s
Versatility | Languages check for Bio2RDF::Wormbase took 60.248199224472046s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2574319839477539s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15755605697631836s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.25782012939453125s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.2656722068786621s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.338002920150757s
License | MR license check for Bio2RDF::Wormbase took 0.2640879154205322s
License | HR license check for Bio2RDF::Wormbase took 60.27947497367859s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.27092552185058594s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.784407615661621s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5964858531951904s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2550501823425293s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2430438995361328s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.3378920555114746s
Performance | Throughput check for Bio2RDF::Wormbase took 10.985297679901123s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.5816373825073242s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.27129387855529785s
Interlinking | skos check for Bio2RDF::Wormbase took 0.518333911895752s
Interlinking | skos check for Bio2RDF::Wormbase took 0.36799120903015137s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.25030517578125s
Currency | Creation date check for Bio2RDF::Wormbase took 0.3458893299102783s
Currency | Modification date check for Bio2RDF::Wormbase took 0.25484466552734375s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 110.60751247406006s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 63.23910689353943s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.42850279808044434s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2417433261871338s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.29553747177124023s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 7.055886268615723s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8925302028656006s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6836161613464355s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.2614457607269287s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.55992341041565s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.445244073867798s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.827815771102905s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3213005065917969s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.66255283355713s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7875146865844727s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.7058680057525635s
Security | Sign check for Bio2RDF::Wormbase took 0.25375890731811523s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 10.748112916946411s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.8453884124755859s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 0.00011301040649414062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 41.01250624656677s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1127.4944388866425s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 1.5266244411468506s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.28551578521728516s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.022628307342529297s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.702278137207031e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 9.298324584960938e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 5.405409574508667s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.059920549392700195s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.6788666248321533s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.02269268035888672s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.0040740966796875e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for biolit took 2.166228771209717s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 8.821487426757812e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.3139011859893799s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.021300554275512695s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.1961669921875e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 6.67572021484375e-05s
INFO | --- Analysis for biolod-pdb took 7.5647053718566895s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5590059757232666s
Availability | VoID file availability check for BioModels RDF took 0.08743000030517578s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.3162221908569336s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.7670135498046875e-05s
Believability | Calculation of trust value for BioModels RDF took 1.3589859008789062e-05s
INFO | --- Analysis for biomodels-rdf took 2.890434980392456s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.326718330383301s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.7543261051177979s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.028265714645385742s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0013687610626220703s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.506111145019531e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1444091796875e-05s
INFO | --- Analysis for Biop took 7.860393047332764s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.322166442871094e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.32166600227355957s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02104353904724121s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.409385681152344e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2636184692382812e-05s
INFO | --- Analysis for Bioportal took 2.962074041366577s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 9.34600830078125e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0003902912139892578s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.5349175930023193s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.000640869140625s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-aao took 10.618150472640991s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 9.632110595703125e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.31061410903930664s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.021786928176879883s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00035572052001953125s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-aba took 13.239567756652832s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 9.465217590332031e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.3291201591491699s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02119755744934082s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015294551849365234s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-acgt took 9.16870641708374s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 9.441375732421875e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0004067420959472656s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.974921464920044s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.021071195602416992s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00036525726318359375s
Believability | Calculation of trust value for Animal natural history and life history took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-adw took 10.411812782287598s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.6629631519317627s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020732641220092773s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0005054473876953125s
Believability | Calculation of trust value for Anatomical Entity Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-aeo took 7.945007562637329s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 9.226799011230469e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.45912861824035645s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009682178497314453s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-aero took 8.148385763168335s
Availability | SPARQL endpoint availability check for AI/RHEUM took 9.918212890625e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.30571436882019043s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004172325134277344s
Believability | Calculation of trust value for AI/RHEUM took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-air took 7.657736301422119s
Availability | SPARQL endpoint availability check for Amino Acid took 9.131431579589844e-05s
Availability | VoID file availability check for Amino Acid took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.7681179046630859s
Reputation | Calculation of the PageRank for Amino Acid took 0.020995140075683594s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00026226043701171875s
Believability | Calculation of trust value for Amino Acid took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-amino-acid took 7.689321756362915s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 9.226799011230469e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.4049105644226074s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002906322479248047s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-apo took 11.552567481994629s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 0.00010180473327636719s
Availability | VoID file availability check for African Traditional Medicine took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.4212222099304199s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02271866798400879s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.001020669937133789s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0003314018249511719s
Believability | Calculation of trust value for African Traditional Medicine took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-atmo took 7.956000089645386s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.673004150390625e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.4639883041381836s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02101302146911621s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.369850158691406e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ato took 7.926693439483643s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.3410148620605469s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.028981447219848633s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0016138553619384766s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.00176239013671875s
Believability | Calculation of trust value for BioAssay Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bao took 14.615793228149414s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 0.00013136863708496094s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.4642956256866455s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020941972732543945s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0004220008850097656s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 11.12630820274353s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.32485461235046387s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003428459167480469s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bcgo took 7.902362108230591s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2929563522338867s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02131366729736328s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014004707336425781s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bdo took 7.53781270980835s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.307894229888916s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.021205425262451172s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005221366882324219s
Believability | Calculation of trust value for Basic Formal Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bfo took 7.61616063117981s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 8.869171142578125e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.34918785095214844s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.033551931381225586s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0015873908996582031s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0012183189392089844s
Believability | Calculation of trust value for Bleeding History Phenotype took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-bho took 8.584657192230225s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 0.00013065338134765625s
Availability | VoID file availability check for Bilateria anatomy took 0.0008065700531005859s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.3850367069244385s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.022853851318359375s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004975795745849609s
Believability | Calculation of trust value for Bilateria anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bila took 8.511729001998901s
Availability | SPARQL endpoint availability check for BIRNLex took 9.465217590332031e-05s
Availability | VoID file availability check for BIRNLex took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.4309072494506836s
Reputation | Calculation of the PageRank for BIRNLex took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0015137195587158203s
Believability | Calculation of trust value for BIRNLex took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-birnlex took 12.67273998260498s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.32131195068359375s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.022777318954467773s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0010683536529541016s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0009026527404785156s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bootstrep took 9.34101128578186s
Availability | SPARQL endpoint availability check for BioPAX took 8.916854858398438e-05s
Availability | VoID file availability check for BioPAX took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for BioPAX took 0.4207901954650879s
Reputation | Calculation of the PageRank for BioPAX took 0.02105712890625s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.942054748535156e-05s
Believability | Calculation of trust value for BioPAX took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-bp took 9.570506572723389s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 0.00010752677917480469s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.3211045265197754s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003490447998046875s
Believability | Calculation of trust value for Biomedical Resource Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-bro_x1 took 6.768296957015991s
Availability | SPARQL endpoint availability check for Spatial Ontology took 9.918212890625e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.48145198822021484s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.03591275215148926s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0014407634735107422s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0003364086151123047s
Believability | Calculation of trust value for Spatial Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bspo took 8.841615676879883s
Availability | SPARQL endpoint availability check for BioTop took 8.893013000488281e-05s
Availability | VoID file availability check for BioTop took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for BioTop took 2.078270196914673s
Reputation | Calculation of the PageRank for BioTop took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006740093231201172s
Believability | Calculation of trust value for BioTop took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bt took 13.915931701660156s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.482269287109375e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0007793903350830078s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.32970738410949707s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020896434783935547s
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.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0009531974792480469s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bto took 7.089083433151245s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 2.5803308486938477s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02455592155456543s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0013499259948730469s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.002443552017211914s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-canco took 11.129382371902466s
Availability | SPARQL endpoint availability check for CAO took 8.96453857421875e-05s
Availability | VoID file availability check for CAO took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for CAO took 1.8628182411193848s
Reputation | Calculation of the PageRank for CAO took 0.023596525192260742s
Interlinking | Calculation of Degree of Connection for CAO took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for CAO took 0.0011477470397949219s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0007712841033935547s
Believability | Calculation of trust value for CAO took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cao took 11.287455320358276s
Availability | SPARQL endpoint availability check for CareLex took 0.00010371208190917969s
Availability | VoID file availability check for CareLex took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for CareLex took 0.3182997703552246s
Reputation | Calculation of the PageRank for CareLex took 0.02130722999572754s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.1021575927734375e-05s
Believability | Calculation of trust value for CareLex took 7.62939453125e-06s
INFO | --- Analysis for bioportal-carelex took 9.580960512161255s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.31352806091308594s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020716428756713867s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007948875427246094s
Believability | Calculation of trust value for Cell Cycle Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cco took 7.444116592407227s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.28860998153686523s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00026607513427734375s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-cdao took 8.130271673202515s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 0.00012755393981933594s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.30911922454833984s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.024237394332885742s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0012090206146240234s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.001009225845336914s
Believability | Calculation of trust value for Chemical entities of biological interest took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-chebi took 9.501882553100586s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 9.036064147949219e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0008602142333984375s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.31118297576904297s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.021739959716796875s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00026988983154296875s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 14.568089723587036s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 5.888938903808594e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.47226572036743164s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02974987030029297s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0017504692077636719s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0010759830474853516s
Believability | Calculation of trust value for Chemical Information Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cheminf took 9.92113971710205s
Availability | SPARQL endpoint availability check for Cell type took 8.749961853027344e-05s
Availability | VoID file availability check for Cell type took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for Cell type took 0.9836654663085938s
Reputation | Calculation of the PageRank for Cell type took 0.02100658416748047s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0004169940948486328s
Believability | Calculation of trust value for Cell type took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cl took 9.219603538513184s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.3657572269439697s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008213520050048828s
Believability | Calculation of trust value for Cell Line Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-clo took 8.150426626205444s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.7920825481414795s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02255535125732422s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0008511543273925781s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0002181529998779297s
Believability | Calculation of trust value for Clinical Measurement Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cmo took 11.189335584640503s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.3313276767730713s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.021074771881103516s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00021123886108398438s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cno took 7.8267834186553955s
Availability | SPARQL endpoint availability check for Wheat trait took 0.00013375282287597656s
Availability | VoID file availability check for Wheat trait took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.46124982833862305s
Reputation | Calculation of the PageRank for Wheat trait took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.53131103515625e-05s
Believability | Calculation of trust value for Wheat trait took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-co_wheat took 9.079784631729126s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 6.0558319091796875e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.3018355369567871s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.021608829498291016s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003840923309326172s
Believability | Calculation of trust value for Cognitive Atlas took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cogat took 6.62011981010437s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.31913280487060547s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.021003007888793945s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0008134841918945312s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cogpo took 10.245757102966309s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 9.179115295410156e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.37853217124938965s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02124309539794922s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004353523254394531s
Believability | Calculation of trust value for Current Procedural Terminology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cpt took 8.106661796569824s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 0.00013327598571777344s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0007774829864501953s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3918600082397461s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.0306546688079834s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.001550912857055664s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0023593902587890625s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-csp took 9.257550716400146s
Availability | SPARQL endpoint availability check for COSTART took 8.940696716308594e-05s
Availability | VoID file availability check for COSTART took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for COSTART took 0.6507468223571777s
Reputation | Calculation of the PageRank for COSTART took 0.02148270606994629s
Interlinking | Calculation of Degree of Connection for COSTART took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0008597373962402344s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0011513233184814453s
Believability | Calculation of trust value for COSTART took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cst took 8.209782123565674s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.38690185546875e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0008995532989501953s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.2962832450866699s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.022771596908569336s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0012066364288330078s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0006604194641113281s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ctcae took 8.700368881225586s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 8.845329284667969e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.3193221092224121s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.0211331844329834s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00044918060302734375s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ctx took 7.470805883407593s
Availability | SPARQL endpoint availability check for Dendritic cell took 9.012222290039062e-05s
Availability | VoID file availability check for Dendritic cell took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.40529704093933105s
Reputation | Calculation of the PageRank for Dendritic cell took 0.02257394790649414s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00032019615173339844s
Believability | Calculation of trust value for Dendritic cell took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-dc_cl took 9.748002290725708s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.821487426757812e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.3094308376312256s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02175736427307129s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.560585021972656e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ddanat took 19.416579961776733s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 9.226799011230469e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0007750988006591797s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.350358247756958s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009634494781494141s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ddi took 13.23838472366333s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 0.00011467933654785156s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.3274214267730713s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02224588394165039s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.606910705566406e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-diagnosticont took 13.188727617263794s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.3110356330871582s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.024669647216796875s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0013532638549804688s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0002589225769042969s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 10.11734652519226s
Availability | SPARQL endpoint availability check for Human disease ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Human disease ontology took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.3301401138305664s
Reputation | Calculation of the PageRank for Human disease ontology took 0.021010160446166992s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006258487701416016s
Believability | Calculation of trust value for Human disease ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-doid took 7.623957633972168s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 1.04453444480896s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008065700531005859s
Believability | Calculation of trust value for Electrocardiography Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ecg took 9.378448009490967s
Availability | SPARQL endpoint availability check for Evidence codes took 8.726119995117188e-05s
Availability | VoID file availability check for Evidence codes took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Evidence codes took 1.0609614849090576s
Reputation | Calculation of the PageRank for Evidence codes took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for Evidence codes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 2.9802322387695312e-05s
Believability | Calculation of trust value for Evidence codes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-eco took 11.630848407745361s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 0.00010228157043457031s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.4774491786956787s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0018017292022705078s
Believability | Calculation of trust value for Experimental Factor Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-efo took 8.15182638168335s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 8.7738037109375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.30361199378967285s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0012221336364746094s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ehda took 11.101887464523315s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 9.036064147949219e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.3248317241668701s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02103400230407715s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007486343383789062s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ehdaa took 11.422959327697754s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 9.417533874511719e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.40119338035583496s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005347728729248047s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 8.980982542037964s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 0.0001270771026611328s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.31998419761657715s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.026846885681152344s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0012383460998535156s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 4.601478576660156e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-emap took 7.668399095535278s
Availability | SPARQL endpoint availability check for Environment Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Environment Ontology took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.32287144660949707s
Reputation | Calculation of the PageRank for Environment Ontology took 0.022190570831298828s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.001068115234375s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0005311965942382812s
Believability | Calculation of trust value for Environment Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-envo took 11.515576362609863s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 8.96453857421875e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.5056102275848389s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02243518829345703s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0003018379211425781s
Believability | Calculation of trust value for Plant environmental conditions took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-eo took 8.837294816970825s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.41138601303100586s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0011997222900390625s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ep took 7.297220468521118s
Availability | SPARQL endpoint availability check for Epilepsy took 0.00012564659118652344s
Availability | VoID file availability check for Epilepsy took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.30237483978271484s
Reputation | Calculation of the PageRank for Epilepsy took 0.02127981185913086s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001499652862548828s
Believability | Calculation of trust value for Epilepsy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-epileponto took 9.414505958557129s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.506111145019531e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.30175185203552246s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020949125289916992s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011723041534423828s
Believability | Calculation of trust value for eagle-i research resource ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ero took 7.015805006027222s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00011157989501953125s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.32500386238098145s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.001155853271484375s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ev took 8.482985258102417s
Availability | SPARQL endpoint availability check for ExO took 9.012222290039062e-05s
Availability | VoID file availability check for ExO took 0.0003476142883300781s
Completeness | Calculation of interlinking completeness for ExO took 2.5591580867767334s
Reputation | Calculation of the PageRank for ExO took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for ExO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ExO took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00025343894958496094s
Believability | Calculation of trust value for ExO took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-exo took 8.309200048446655s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 8.96453857421875e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.9603285789489746s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020747900009155273s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.0001163482666015625s
Believability | Calculation of trust value for Fungal gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fao took 9.774446249008179s
Availability | SPARQL endpoint availability check for Biological imaging methods took 8.988380432128906e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.33244943618774414s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00019860267639160156s
Believability | Calculation of trust value for Biological imaging methods took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fbbi took 7.485477924346924s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 9.751319885253906e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0008006095886230469s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.6116485595703125s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.000675201416015625s
Believability | Calculation of trust value for Drosophila gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fbbt took 6.8517515659332275s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 9.417533874511719e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.48191356658935547s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.021837234497070312s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004496574401855469s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fbcv took 12.861834526062012s
Availability | SPARQL endpoint availability check for Drosophila development took 0.00015687942504882812s
Availability | VoID file availability check for Drosophila development took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.4451711177825928s
Reputation | Calculation of the PageRank for Drosophila development took 0.023769378662109375s
Interlinking | Calculation of Degree of Connection for Drosophila development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.291534423828125e-05s
Believability | Calculation of trust value for Drosophila development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fbdv took 8.69443941116333s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.893013000488281e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.3017768859863281s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02073836326599121s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003743171691894531s
Believability | Calculation of trust value for Fly taxonomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-fbsp took 8.478951454162598s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 8.821487426757812e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.33747148513793945s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.023296594619750977s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0014662742614746094s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0003287792205810547s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 9.39295220375061s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 1.082423210144043s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020691394805908203s
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.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004229545593261719s
Believability | Calculation of trust value for Family Health History Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fhho took 8.573034286499023s
Availability | SPARQL endpoint availability check for Influenza Ontology took 0.0001361370086669922s
Availability | VoID file availability check for Influenza Ontology took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.3571743965148926s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.0211179256439209s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001054525375366211s
Believability | Calculation of trust value for Influenza Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-flu took 6.509213447570801s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 8.654594421386719e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.31125569343566895s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.021055221557617188s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 7.414817810058594e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fma took 7.0319743156433105s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.4799075126647949s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.021088838577270508s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00014495849609375s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fypo took 12.629661083221436s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.8398921489715576s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.021143436431884766s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.846687316894531e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-geospecies took 8.181155920028687s
Availability | SPARQL endpoint availability check for General Formal Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.3176083564758301s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.022660017013549805s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016570091247558594s
Believability | Calculation of trust value for General Formal Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-gfo took 7.849186658859253s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 8.988380432128906e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.49522876739501953s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.021712303161621094s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006344318389892578s
Believability | Calculation of trust value for General Formal Ontology: Biology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-gfo-bio took 6.836621999740601s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 9.036064147949219e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 1.734614610671997s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.02089715003967285s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0008304119110107422s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008902549743652344s
Believability | Calculation of trust value for Gene Ontology Extension took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-go_x1 took 8.727882385253906s
Availability | SPARQL endpoint availability check for Gene Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Gene Ontology took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.5485930442810059s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008420944213867188s
Believability | Calculation of trust value for Gene Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-go_x2 took 7.424657344818115s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 9.036064147949219e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0008904933929443359s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.6885049343109131s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02172565460205078s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.1948089599609375e-05s
Believability | Calculation of trust value for Cereal Plant Development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gro took 8.4289231300354s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.696846008300781e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 2.350436210632324s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004527568817138672s
Believability | Calculation of trust value for Cereal plant gross anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-gro_x1 took 9.792468786239624s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 9.322166442871094e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.3144383430480957s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.022147417068481445s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0008218288421630859s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0008223056793212891s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-gro_x2 took 10.450215578079224s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.32109856605529785s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02233266830444336s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0010628700256347656s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0007014274597167969s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-hao took 10.397027015686035s
Availability | SPARQL endpoint availability check for HCPCS took 8.96453857421875e-05s
Availability | VoID file availability check for HCPCS took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for HCPCS took 1.2248258590698242s
Reputation | Calculation of the PageRank for HCPCS took 0.02236771583557129s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0008840560913085938s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.000278472900390625s
Believability | Calculation of trust value for HCPCS took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hcpcs took 16.173006057739258s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.315376281738281e-05s
Availability | VoID file availability check for Health Level Seven took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.5728859901428223s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02213907241821289s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0013179779052734375s
Believability | Calculation of trust value for Health Level Seven took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-hl7 took 10.72330093383789s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 8.940696716308594e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0003554821014404297s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.5631446838378906s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.023592233657836914s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0012078285217285156s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00045990943908691406s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hlth_indics took 7.488617658615112s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 8.96453857421875e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2985982894897461s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.035408973693847656s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0014119148254394531s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 5.7697296142578125e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hom took 13.542058944702148s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 9.131431579589844e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.33254480361938477s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.024687767028808594s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0012934207916259766s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 4.1961669921875e-05s
Believability | Calculation of trust value for HOM-HARVARD took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hom_harvard took 11.048310279846191s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 2.03865909576416s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006747245788574219s
Believability | Calculation of trust value for Human Phenotype Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hp_x1 took 13.70871901512146s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 9.441375732421875e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 1.3036861419677734s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020748376846313477s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.00107574462890625s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hpio took 9.475463151931763s
Availability | SPARQL endpoint availability check for HUGO took 9.632110595703125e-05s
Availability | VoID file availability check for HUGO took 0.0009756088256835938s
Completeness | Calculation of interlinking completeness for HUGO took 0.4181385040283203s
Reputation | Calculation of the PageRank for HUGO took 0.024848222732543945s
Interlinking | Calculation of Degree of Connection for HUGO took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for HUGO took 0.001302480697631836s
Interlinking | Calculation of Clustering coefficient for HUGO took 0.00011801719665527344s
Believability | Calculation of trust value for HUGO took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hugo took 22.43956208229065s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 6.679738759994507s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02155017852783203s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006811618804931641s
Believability | Calculation of trust value for Information Artifact Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-iao took 31.278701305389404s
Availability | SPARQL endpoint availability check for ICD10 took 9.1552734375e-05s
Availability | VoID file availability check for ICD10 took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for ICD10 took 0.33490657806396484s
Reputation | Calculation of the PageRank for ICD10 took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008547306060791016s
Believability | Calculation of trust value for ICD10 took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-icd10 took 13.175704002380371s
Availability | SPARQL endpoint availability check for ICD10CM took 9.298324584960938e-05s
Availability | VoID file availability check for ICD10CM took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.5275843143463135s
Reputation | Calculation of the PageRank for ICD10CM took 0.020982027053833008s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006327629089355469s
Believability | Calculation of trust value for ICD10CM took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icd10cm took 9.040586948394775s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 8.702278137207031e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.32108306884765625s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02103114128112793s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.000164031982421875s
Believability | Calculation of trust value for ICD-10-PCS took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icd10pcs took 12.038906574249268s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 0.00014901161193847656s
Availability | VoID file availability check for International Classification of Diseases took 0.0008618831634521484s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 1.9061510562896729s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.026200056076049805s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0014052391052246094s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0008835792541503906s
Believability | Calculation of trust value for International Classification of Diseases took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-icd9cm took 11.650066137313843s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 9.512901306152344e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.8854186534881592s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.0278933048248291s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0013666152954101562s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0006189346313476562s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icf_x1 took 8.204943418502808s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 8.845329284667969e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 1.4762444496154785s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012946128845214844s
Believability | Calculation of trust value for International Classification for Nursing Practice took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-icnp took 7.858449220657349s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 9.584426879882812e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 3.3795218467712402s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004649162292480469s
Believability | Calculation of trust value for International Classification of Primary Care took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-icpc took 12.730999946594238s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 0.00010371208190917969s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.30982160568237305s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008752346038818359s
Believability | Calculation of trust value for ICPC-2 PLUS took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icpc2p took 9.489314794540405s
Availability | SPARQL endpoint availability check for ICPS Network took 9.131431579589844e-05s
Availability | VoID file availability check for ICPS Network took 0.0003485679626464844s
Completeness | Calculation of interlinking completeness for ICPS Network took 2.5884509086608887s
Reputation | Calculation of the PageRank for ICPS Network took 0.023626089096069336s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0012290477752685547s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00030803680419921875s
Believability | Calculation of trust value for ICPS Network took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icps took 11.28043508529663s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.33626580238342285s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02203226089477539s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0011758804321289062s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0010693073272705078s
Believability | Calculation of trust value for Infectious Disease Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ido took 9.333056211471558s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 0.00010967254638671875s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.3175029754638672s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0012264251708984375s
Believability | Calculation of trust value for Brucellosis Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-idobru took 10.421759843826294s
Availability | SPARQL endpoint availability check for Malaria Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.5536580085754395s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.021028518676757812s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013225078582763672s
Believability | Calculation of trust value for Malaria Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-idomal took 11.800789833068848s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 9.107589721679688e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.7911167144775391s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.021345853805541992s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00035119056701660156s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-iev took 10.080143928527832s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 8.940696716308594e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 3.3052992820739746s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0008072853088378906s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00016808509826660156s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-imgt took 9.606600046157837s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 6.4849853515625e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 1.8353893756866455s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.02088308334350586s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005502700805664062s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-imr took 12.235169887542725s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.4156954288482666s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020911455154418945s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007977485656738281s
Believability | Calculation of trust value for Interaction Network Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ino took 8.799266576766968s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 8.749961853027344e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.33358120918273926s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.021699905395507812s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0008184909820556641s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.504753112792969e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-invertebrata took 22.810263633728027s
Availability | SPARQL endpoint availability check for IxnO took 4.6253204345703125e-05s
Availability | VoID file availability check for IxnO took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for IxnO took 0.3800346851348877s
Reputation | Calculation of the PageRank for IxnO took 0.021399736404418945s
Interlinking | Calculation of Degree of Connection for IxnO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00022149085998535156s
Believability | Calculation of trust value for IxnO took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ixno took 10.072635412216187s
Availability | SPARQL endpoint availability check for SysMO-JERM took 8.7738037109375e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0004127025604248047s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 4.58797550201416s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020901203155517578s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.000408172607421875s
Believability | Calculation of trust value for SysMO-JERM took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-jerm took 15.537627696990967s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.35008668899536133s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-kisao took 9.357731580734253s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 8.749961853027344e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.3177626132965088s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02208876609802246s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0011110305786132812s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00027823448181152344s
Believability | Calculation of trust value for Loggerhead nesting took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-lhn took 7.968843936920166s
Availability | SPARQL endpoint availability check for Lipid Ontology took 9.965896606445312e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 1.4923977851867676s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020384788513183594s
Believability | Calculation of trust value for Lipid Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-lipro took 10.395609378814697s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.601478576660156e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 1.2373993396759033s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.021082401275634766s
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.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0019059181213378906s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-lnc took 12.457600831985474s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 2.5730960369110107s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.021063566207885742s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006844997406005859s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ma took 11.640709161758423s
Availability | SPARQL endpoint availability check for Multiple alignment took 7.534027099609375e-05s
Availability | VoID file availability check for Multiple alignment took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.3024275302886963s
Reputation | Calculation of the PageRank for Multiple alignment took 0.029424428939819336s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0015993118286132812s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.000331878662109375s
Believability | Calculation of trust value for Multiple alignment took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-mao took 8.810508966445923s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.916854858398438e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.3414921760559082s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020825862884521484s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007164478302001953s
Believability | Calculation of trust value for Minimal anatomical terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mat took 10.526102304458618s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.821487426757812e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.47843050956726074s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.021109342575073242s
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.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004470348358154297s
Believability | Calculation of trust value for Breast tissue cell lines took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mcbcc took 11.657233238220215s
Availability | SPARQL endpoint availability check for Cell line ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.5271046161651611s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02087259292602539s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007810592651367188s
Believability | Calculation of trust value for Cell line ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mccl took 13.020544052124023s
Availability | SPARQL endpoint availability check for Cell line ontology took 5.793571472167969e-05s
Availability | VoID file availability check for Cell line ontology took 0.000701904296875s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.3583064079284668s
Reputation | Calculation of the PageRank for Cell line ontology took 0.023914337158203125s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 3.361701965332031e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0012099742889404297s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0017478466033935547s
Believability | Calculation of trust value for Cell line ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 10.657108545303345s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.601478576660156e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.3107485771179199s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.021265268325805664s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002532005310058594s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mcv took 7.427225589752197s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.696846008300781e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.43167543411254883s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00019860267639160156s
Believability | Calculation of trust value for Master Drug Data Base took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mddb took 11.953136205673218s
Availability | SPARQL endpoint availability check for MedDRA took 4.5299530029296875e-05s
Availability | VoID file availability check for MedDRA took 0.00041103363037109375s
Completeness | Calculation of interlinking completeness for MedDRA took 0.32080507278442383s
Reputation | Calculation of the PageRank for MedDRA took 0.020897626876831055s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011935234069824219s
Believability | Calculation of trust value for MedDRA took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mdr took 7.178499937057495s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 9.202957153320312e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.00040841102600097656s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.4752480983734131s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.0213167667388916s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009851455688476562s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-medlineplus took 8.104773759841919s
Availability | SPARQL endpoint availability check for MeGO took 0.00016546249389648438s
Availability | VoID file availability check for MeGO took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for MeGO took 1.5495214462280273s
Reputation | Calculation of the PageRank for MeGO took 0.021049976348876953s
Interlinking | Calculation of Degree of Connection for MeGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00015497207641601562s
Believability | Calculation of trust value for MeGO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mego took 11.98082709312439s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 8.869171142578125e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 5.034456014633179s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.001867055892944336s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mesh-owl took 14.979698181152344s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0008599758148193359s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 1.790705680847168s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0008134841918945312s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006666183471679688s
Believability | Calculation of trust value for Mental Functioning Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mf took 10.098992824554443s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 9.059906005859375e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.46556544303894043s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02168726921081543s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.001310110092163086s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0007431507110595703s
Believability | Calculation of trust value for Medaka fish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mfo took 9.044684171676636s
Availability | SPARQL endpoint availability check for Emotion Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0003669261932373047s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.29923391342163086s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007812976837158203s
Believability | Calculation of trust value for Emotion Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mfoem took 8.845717906951904s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.7707388401031494s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.021301746368408203s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011563301086425781s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mhc took 8.984866857528687s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.5299530029296875e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0003695487976074219s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.46120691299438477s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.02196955680847168s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.001039743423461914s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0008292198181152344s
Believability | Calculation of trust value for Protein-protein interaction took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mi took 9.022391319274902s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 8.654594421386719e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.3299226760864258s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.02500319480895996s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0013136863708496094s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0009899139404296875s
Believability | Calculation of trust value for Mosquito insecticide resistance took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-miro took 12.61459231376648s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 9.942054748535156e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.3341095447540283s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001533031463623047s
Believability | Calculation of trust value for Measurement Method Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mmo took 21.41780924797058s
Availability | SPARQL endpoint availability check for MGED Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for MGED Ontology took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.3089604377746582s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021485090255737305s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0004069805145263672s
Believability | Calculation of trust value for MGED Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mo took 18.636953830718994s
Availability | SPARQL endpoint availability check for Protein modification took 0.00011801719665527344s
Availability | VoID file availability check for Protein modification took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Protein modification took 0.3009355068206787s
Reputation | Calculation of the PageRank for Protein modification took 0.021538734436035156s
Interlinking | Calculation of Degree of Connection for Protein modification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00023412704467773438s
Believability | Calculation of trust value for Protein modification took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mod took 11.847310781478882s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 9.131431579589844e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 1.7189040184020996s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0007147789001464844s
Believability | Calculation of trust value for Mammalian phenotype took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mp took 11.286732196807861s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.649162292480469e-05s
Availability | VoID file availability check for Mouse pathology took 0.0008108615875244141s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.3257308006286621s
Reputation | Calculation of the PageRank for Mouse pathology took 0.021256685256958008s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0005397796630859375s
Believability | Calculation of trust value for Mouse pathology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mpath took 10.62789273262024s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.410743713378906e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.8544712066650391s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.023152828216552734s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0013661384582519531s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0005903244018554688s
Believability | Calculation of trust value for Mass spectrometry took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ms took 9.662895917892456s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 9.274482727050781e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 1.8506674766540527s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0019478797912597656s
Believability | Calculation of trust value for Medical Subject Headings took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-msh took 17.5858473777771s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 9.036064147949219e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.294872522354126s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.021828174591064453s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0009348392486572266s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00022530555725097656s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-mthch took 9.17673373222351s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 9.584426879882812e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.00034236907958984375s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 3.8337161540985107s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.021538257598876953s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008139610290527344s
Believability | Calculation of trust value for Natural Products Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-natpro took 10.327975988388062s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 8.559226989746094e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0004012584686279297s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.29877495765686035s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.021323680877685547s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008754730224609375s
Believability | Calculation of trust value for NCBI organismal classification took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 10.93069839477539s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.845329284667969e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00032448768615722656s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 1.0048949718475342s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02159905433654785s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020906925201416016s
Believability | Calculation of trust value for NCI Thesaurus took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ncit took 8.243831157684326s
Availability | SPARQL endpoint availability check for National Drug Data File took 8.988380432128906e-05s
Availability | VoID file availability check for National Drug Data File took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.9559333324432373s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006375312805175781s
Believability | Calculation of trust value for National Drug Data File took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nddf took 8.12067198753357s
Availability | SPARQL endpoint availability check for National Drug File took 9.059906005859375e-05s
Availability | VoID file availability check for National Drug File took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for National Drug File took 0.43407607078552246s
Reputation | Calculation of the PageRank for National Drug File took 0.02297186851501465s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012581348419189453s
Believability | Calculation of trust value for National Drug File took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ndfrt took 9.626054048538208s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 9.036064147949219e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.3228461742401123s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02105998992919922s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0008442401885986328s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0013222694396972656s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 8.505309820175171s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.3629631996154785s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.0207216739654541s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006639957427978516s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-neomark took 7.779870986938477s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.44416284561157227s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02112746238708496s
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.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012946128845214844s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-neomarkontology took 13.10999083518982s
Availability | SPARQL endpoint availability check for NIFSTD took 9.417533874511719e-05s
Availability | VoID file availability check for NIFSTD took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.33745265007019043s
Reputation | Calculation of the PageRank for NIFSTD took 0.02189922332763672s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.52587890625e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0011110305786132812s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0021872520446777344s
Believability | Calculation of trust value for NIFSTD took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nif took 11.784159660339355s
Availability | SPARQL endpoint availability check for NIF Cell took 9.059906005859375e-05s
Availability | VoID file availability check for NIF Cell took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for NIF Cell took 1.4738101959228516s
Reputation | Calculation of the PageRank for NIF Cell took 0.022472143173217773s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0008966922760009766s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0014655590057373047s
Believability | Calculation of trust value for NIF Cell took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-nif_cell took 11.29670262336731s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 9.202957153320312e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.4360072612762451s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0010688304901123047s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0016112327575683594s
Believability | Calculation of trust value for NIF Dysfunction took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 7.448901414871216s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.3033788204193115s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.025000572204589844s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0013964176177978516s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0007710456848144531s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nigo took 6.571958780288696s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.845329284667969e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.37923765182495117s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.021156787872314453s
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.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005698204040527344s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 1.811981201171875e-05s
INFO | --- Analysis for bioportal-nmr took 8.813884258270264s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.5646932125091553s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.022186756134033203s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011277198791503906s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 7.581136465072632s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0008111000061035156s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 3.4497230052948s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.021386146545410156s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012187957763671875s
Believability | Calculation of trust value for NanoParticle Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-npo took 11.384089469909668s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 9.632110595703125e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.001428842544555664s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.3178267478942871s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.0218503475189209s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007584095001220703s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-oae took 7.13793683052063s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 9.274482727050781e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0007863044738769531s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 1.3712396621704102s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02116227149963379s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014960765838623047s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-obi took 8.176943063735962s
Availability | SPARQL endpoint availability check for OBOE took 5.698204040527344e-05s
Availability | VoID file availability check for OBOE took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for OBOE took 0.31362271308898926s
Reputation | Calculation of the PageRank for OBOE took 0.02277684211730957s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0008645057678222656s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001373291015625s
Believability | Calculation of trust value for OBOE took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-oboe took 7.2710020542144775s
Availability | SPARQL endpoint availability check for OBOE SBC took 0.00010132789611816406s
Availability | VoID file availability check for OBOE SBC took 0.0013234615325927734s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.5350193977355957s
Reputation | Calculation of the PageRank for OBOE SBC took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008337497711181641s
Believability | Calculation of trust value for OBOE SBC took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 7.352291584014893s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 9.059906005859375e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0012602806091308594s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 1.209385871887207s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.021509408950805664s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0006923675537109375s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ocre took 10.821180582046509s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 9.179115295410156e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.5171871185302734s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.022853612899780273s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008711814880371094s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-odgi took 7.4184794425964355s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 8.988380432128906e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 1.6656537055969238s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02118825912475586s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0009057521820068359s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0010366439819335938s
Believability | Calculation of trust value for Ontology for Genetic Interval took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ogi took 18.4495689868927s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 9.036064147949219e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 2.6732401847839355s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.021149158477783203s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0009381771087646484s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0003952980041503906s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ogmd took 16.513493061065674s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 0.0001277923583984375s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.508934736251831s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.024983644485473633s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0012149810791015625s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0008521080017089844s
Believability | Calculation of trust value for Ontology for General Medical Science took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ogms took 7.354557275772095s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 0.000102996826171875s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.5422375202178955s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011913776397705078s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-omim took 6.7217323780059814s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 9.131431579589844e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.30842041969299316s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.02097463607788086s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0004069805145263672s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-omit took 12.745888948440552s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 0.00011563301086425781s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.33118772506713867s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006237030029296875s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-omrse took 11.550081253051758s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 5.0067901611328125e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.9609935283660889s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.022017240524291992s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0009832382202148438s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0009605884552001953s
Believability | Calculation of trust value for Ontology of Data Mining took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ontodm took 12.250272750854492s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 8.678436279296875e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.4011526107788086s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00025773048400878906s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ontodt took 9.275421142578125s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 9.131431579589844e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.30243635177612305s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020840883255004883s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006318092346191406s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ontoorpha took 9.923418045043945s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 9.179115295410156e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.44878554344177246s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0010340213775634766s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0010900497436523438s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-opl took 7.955154895782471s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.7206878662109375e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.4307291507720947s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008897781372070312s
Believability | Calculation of trust value for Phenotypic quality took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-pato took 11.561345100402832s
Availability | SPARQL endpoint availability check for Physician Data Query took 5.5789947509765625e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.3200850486755371s
Reputation | Calculation of the PageRank for Physician Data Query took 0.03268909454345703s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0014698505401611328s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0012831687927246094s
Believability | Calculation of trust value for Physician Data Query took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pdq took 11.160271406173706s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 6.008148193359375e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.40586304664611816s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008530616760253906s
Believability | Calculation of trust value for Pediatric Terminology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pedterm took 6.449276685714722s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.000743865966796875s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.365588903427124s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.02687692642211914s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0020225048065185547s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0004067420959472656s
Believability | Calculation of trust value for Parasite Experiment Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-peo took 8.043617010116577s
Availability | SPARQL endpoint availability check for PHARE took 8.726119995117188e-05s
Availability | VoID file availability check for PHARE took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for PHARE took 0.3341398239135742s
Reputation | Calculation of the PageRank for PHARE took 0.0222017765045166s
Interlinking | Calculation of Degree of Connection for PHARE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006515979766845703s
Believability | Calculation of trust value for PHARE took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-phare took 7.7995123863220215s
Availability | SPARQL endpoint availability check for PKO_Re took 9.059906005859375e-05s
Availability | VoID file availability check for PKO_Re took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for PKO_Re took 4.069108009338379s
Reputation | Calculation of the PageRank for PKO_Re took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for PKO_Re took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001723766326904297s
Believability | Calculation of trust value for PKO_Re took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pko took 12.778987884521484s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for PMA 2010 took 0.0007228851318359375s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.5108635425567627s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02121257781982422s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009906291961669922s
Believability | Calculation of trust value for PMA 2010 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pma took 10.63049030303955s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 8.96453857421875e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.4207024574279785s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.021121740341186523s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001780986785888672s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-pmr took 9.059888124465942s
Availability | SPARQL endpoint availability check for Plant Anatomy took 9.036064147949219e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.3106496334075928s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00042510032653808594s
Believability | Calculation of trust value for Plant Anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-po took 10.490471601486206s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.7738037109375e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.297987699508667s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02229022979736328s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0010967254638671875s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 9.846687316894531e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-po_x1 took 8.418765306472778s
Availability | SPARQL endpoint availability check for Plant Ontology took 0.0001666545867919922s
Availability | VoID file availability check for Plant Ontology took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.37691330909729004s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004630088806152344s
Believability | Calculation of trust value for Plant Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-po_x2 took 8.605762958526611s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 9.441375732421875e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.8384201526641846s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.021120071411132812s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0009284019470214844s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0007672309875488281s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-pr took 9.48179817199707s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 9.012222290039062e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0014531612396240234s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 1.2387933731079102s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.023335933685302734s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00029015541076660156s
Believability | Calculation of trust value for Proteomics data and process provenance took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-propreo took 7.605123281478882s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.3284909725189209s
Reputation | Calculation of the PageRank for Pathway ontology took 0.021119356155395508s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00013375282287597656s
Believability | Calculation of trust value for Pathway ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pw took 14.227071762084961s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.46225547790527344s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-qibo took 7.7059454917907715s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 9.34600830078125e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.5074238777160645s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0018105506896972656s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-rcd took 8.318760871887207s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0007674694061279297s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.32074403762817383s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02625417709350586s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0013532638549804688s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00019478797912597656s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-rctontology took 6.797577619552612s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 9.1552734375e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2892625331878662s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02224588394165039s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.751319885253906e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-repo took 6.3608129024505615s
Availability | SPARQL endpoint availability check for Physico-chemical process took 8.988380432128906e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.3064582347869873s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02260422706604004s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00022792816162109375s
Believability | Calculation of trust value for Physico-chemical process took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rex took 6.669320821762085s
Availability | SPARQL endpoint availability check for RadLex took 8.821487426757812e-05s
Availability | VoID file availability check for RadLex took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for RadLex took 0.32012200355529785s
Reputation | Calculation of the PageRank for RadLex took 0.02103257179260254s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0008218288421630859s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.00159454345703125s
Believability | Calculation of trust value for RadLex took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-rid took 7.8090739250183105s
Availability | SPARQL endpoint availability check for RNA ontology took 0.00010395050048828125s
Availability | VoID file availability check for RNA ontology took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.4639005661010742s
Reputation | Calculation of the PageRank for RNA ontology took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0008265972137451172s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005962848663330078s
Believability | Calculation of trust value for RNA ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rnao took 6.586354732513428s
Availability | SPARQL endpoint availability check for Role Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Role Ontology took 0.00036406517028808594s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.3206930160522461s
Reputation | Calculation of the PageRank for Role Ontology took 0.023114919662475586s
Interlinking | Calculation of Degree of Connection for Role Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00021648406982421875s
Believability | Calculation of trust value for Role Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-roleo took 6.909756422042847s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.3351454734802246s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.024782896041870117s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0013091564178466797s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0002491474151611328s
Believability | Calculation of trust value for Rat Strain Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rs took 7.231074333190918s
Availability | SPARQL endpoint availability check for RxNORM took 8.726119995117188e-05s
Availability | VoID file availability check for RxNORM took 0.0007352828979492188s
Completeness | Calculation of interlinking completeness for RxNORM took 2.0778727531433105s
Reputation | Calculation of the PageRank for RxNORM took 0.02138805389404297s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0010726451873779297s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0007507801055908203s
Believability | Calculation of trust value for RxNORM took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rxnorm took 13.509370803833008s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 6.008148193359375e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0008451938629150391s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.30790257453918457s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.021390914916992188s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0012667179107666016s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-sao took 8.742601871490479s
Availability | SPARQL endpoint availability check for Systems Biology took 9.822845458984375e-05s
Availability | VoID file availability check for Systems Biology took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.38190579414367676s
Reputation | Calculation of the PageRank for Systems Biology took 0.0215301513671875s
Interlinking | Calculation of Degree of Connection for Systems Biology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004596710205078125s
Believability | Calculation of trust value for Systems Biology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sbo took 7.56665563583374s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0003917217254638672s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.3040754795074463s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.021214008331298828s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.0001239776611328125s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-sbro took 7.676393032073975s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.3057281970977783s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02136826515197754s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.001420736312866211s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sdo took 8.861665487289429s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 9.608268737792969e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.3710618019104004s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.021933794021606445s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003719329833984375s
Believability | Calculation of trust value for Sample processing and separation techniques took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-sep took 7.576230049133301s
Availability | SPARQL endpoint availability check for Student Health Record took 4.601478576660156e-05s
Availability | VoID file availability check for Student Health Record took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.5701851844787598s
Reputation | Calculation of the PageRank for Student Health Record took 0.021130800247192383s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0009810924530029297s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0005791187286376953s
Believability | Calculation of trust value for Student Health Record took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-shr took 13.393511533737183s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.4138646125793457s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.024391889572143555s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0012083053588867188s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0014872550964355469s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sio took 15.794463634490967s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.96453857421875e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.468350887298584s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02373337745666504s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0011467933654785156s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0003032684326171875s
Believability | Calculation of trust value for Situation-Based Access Control took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-sitbac took 7.1967198848724365s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 8.893013000488281e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.5903663635253906s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019903182983398438s
Believability | Calculation of trust value for SNOMED Clinical Terms took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-snomedct took 11.79861307144165s
Availability | SPARQL endpoint availability check for SNP-Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.3220221996307373s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02101588249206543s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007045269012451172s
Believability | Calculation of trust value for SNP-Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-snpo took 8.596327781677246s
Availability | SPARQL endpoint availability check for Sequence types and features took 9.369850158691406e-05s
Availability | VoID file availability check for Sequence types and features took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.5300652980804443s
Reputation | Calculation of the PageRank for Sequence types and features took 0.02676844596862793s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0014557838439941406s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0007872581481933594s
Believability | Calculation of trust value for Sequence types and features took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-so_x1 took 6.780885696411133s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.96453857421875e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.40550756454467773s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.021902084350585938s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0008478164672851562s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0016651153564453125s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sopharm took 8.449505805969238s
Availability | SPARQL endpoint availability check for SoyOntology took 8.749961853027344e-05s
Availability | VoID file availability check for SoyOntology took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.29662513732910156s
Reputation | Calculation of the PageRank for SoyOntology took 0.02123546600341797s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001385211944580078s
Believability | Calculation of trust value for SoyOntology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-soy took 9.257140874862671s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Spider Ontology took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.30638551712036133s
Reputation | Calculation of the PageRank for Spider Ontology took 0.021676063537597656s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003731250762939453s
Believability | Calculation of trust value for Spider Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-spd took 12.033164024353027s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 1.5466125011444092s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.026256322860717773s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0013380050659179688s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0003960132598876953s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-spto took 12.718162059783936s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.29791951179504395s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02173757553100586s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004696846008300781s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sso took 7.740068435668945s
Availability | SPARQL endpoint availability check for Software Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Software Ontology took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.31905460357666016s
Reputation | Calculation of the PageRank for Software Ontology took 0.03168797492980957s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.001300811767578125s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0006546974182128906s
Believability | Calculation of trust value for Software Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-swo took 8.457971811294556s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.863739013671875e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.30751705169677734s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02187037467956543s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00025653839111328125s
Believability | Calculation of trust value for Tick gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tads took 8.458588361740112s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 1.2145462036132812s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.022968769073486328s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.001005411148071289s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0010747909545898438s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tao took 7.566990613937378s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.38690185546875e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.3142111301422119s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02623438835144043s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0014433860778808594s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 0.0001399517059326172s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-taxrank took 7.253803014755249s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 0.00010013580322265625s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.31760525703430176s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02192544937133789s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 9.059906005859375e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-teddy took 9.507889747619629s
Availability | SPARQL endpoint availability check for Time Event Ontology took 9.322166442871094e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.31394529342651367s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.021736621856689453s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0010197162628173828s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0010063648223876953s
Believability | Calculation of trust value for Time Event Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-teo took 8.234756708145142s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.940696716308594e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.4672830104827881s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.02439093589782715s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0012714862823486328s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0005137920379638672s
Believability | Calculation of trust value for Mosquito gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-tgma took 9.48132848739624s
Availability | SPARQL endpoint availability check for thesaurus took 0.00011610984802246094s
Availability | VoID file availability check for thesaurus took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for thesaurus took 1.6710007190704346s
Reputation | Calculation of the PageRank for thesaurus took 0.021718740463256836s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0012462139129638672s
Interlinking | Calculation of Clustering coefficient for thesaurus took 9.751319885253906e-05s
Believability | Calculation of trust value for thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-thesaurus took 15.82370901107788s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 9.799003601074219e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.00036787986755371094s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.3079490661621094s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003600120544433594s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 8.159640789031982s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 9.465217590332031e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.00035572052001953125s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.31916356086730957s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020980358123779297s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0010333061218261719s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0010097026824951172s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tmo took 13.16526746749878s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0012390613555908203s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 7.704348802566528s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.0001773834228515625s
Believability | Calculation of trust value for Plant Trait Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-to took 19.63851237297058s
Availability | SPARQL endpoint availability check for TOK_Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 1.9970881938934326s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001857280731201172s
Believability | Calculation of trust value for TOK_Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tok took 19.390292644500732s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 8.916854858398438e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 1.1649494171142578s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.021289587020874023s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00021076202392578125s
Believability | Calculation of trust value for Teleost taxonomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tto took 9.4573233127594s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.43842077255249023s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.024294614791870117s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0012276172637939453s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0013086795806884766s
Believability | Calculation of trust value for Uber anatomy ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-uberon took 9.148101091384888s
Availability | SPARQL endpoint availability check for Units Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Units Ontology took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Units Ontology took 1.8001234531402588s
Reputation | Calculation of the PageRank for Units Ontology took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00022363662719726562s
Believability | Calculation of trust value for Units Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-unitsontology took 11.159100532531738s
Availability | SPARQL endpoint availability check for Units of measurement took 9.322166442871094e-05s
Availability | VoID file availability check for Units of measurement took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Units of measurement took 3.6380178928375244s
Reputation | Calculation of the PageRank for Units of measurement took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00029730796813964844s
Believability | Calculation of trust value for Units of measurement took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-uo took 16.94830584526062s
Availability | SPARQL endpoint availability check for VANDF took 4.3392181396484375e-05s
Availability | VoID file availability check for VANDF took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for VANDF took 0.7851455211639404s
Reputation | Calculation of the PageRank for VANDF took 0.02117013931274414s
Interlinking | Calculation of Degree of Connection for VANDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007243156433105469s
Believability | Calculation of trust value for VANDF took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-vandf took 13.891840934753418s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 9.34600830078125e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0012640953063964844s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 1.7561120986938477s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.021489620208740234s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00043892860412597656s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-vao took 12.264111995697021s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 8.893013000488281e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.31804680824279785s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0007100105285644531s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-vhog took 8.5880708694458s
Availability | SPARQL endpoint availability check for VIVO took 0.000141143798828125s
Availability | VoID file availability check for VIVO took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for VIVO took 0.3055438995361328s
Reputation | Calculation of the PageRank for VIVO took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for VIVO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003676414489746094s
Believability | Calculation of trust value for VIVO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-vivo took 6.814937591552734s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.41791272163391113s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02231574058532715s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0013544559478759766s
Believability | Calculation of trust value for Vaccine Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-vo took 7.063683271408081s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 2.5397462844848633s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.021670103073120117s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0008432865142822266s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002560615539550781s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-vt took 18.12226700782776s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 9.274482727050781e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0003898143768310547s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.44294118881225586s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.021908283233642578s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.001058816909790039s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0006308555603027344s
Believability | Calculation of trust value for C. elegans gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-wbbt took 14.759714365005493s
Availability | SPARQL endpoint availability check for C. elegans development took 8.96453857421875e-05s
Availability | VoID file availability check for C. elegans development took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for C. elegans development took 2.686307668685913s
Reputation | Calculation of the PageRank for C. elegans development took 0.021113157272338867s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.982948303222656e-05s
Believability | Calculation of trust value for C. elegans development took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-wbls took 14.372363328933716s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.863739013671875e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 3.099635601043701s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.021394729614257812s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.34600830078125e-05s
Believability | Calculation of trust value for C. elegans phenotype took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-wbphenotype took 14.589177131652832s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 9.1552734375e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.4165916442871094s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006413459777832031s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-who took 8.89943552017212s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 0.00010180473327636719s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.45064854621887207s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0007348060607910156s
Believability | Calculation of trust value for Xenopus anatomy and development took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-xao took 17.944200038909912s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.32959866523742676s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.022626399993896484s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0009844303131103516s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00031113624572753906s
Believability | Calculation of trust value for Experimental Conditions Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-xco took 23.64838743209839s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 5.7220458984375e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 26.26621174812317s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.032422780990600586s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 5.078315734863281e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0016169548034667969s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0004372596740722656s
Believability | Calculation of trust value for Yeast phenotypes took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ypo took 94.12347197532654s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.96453857421875e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 5.307728290557861s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.023836135864257812s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0012340545654296875s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0009679794311523438s
Believability | Calculation of trust value for Zebrafish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-zfa took 139.44748210906982s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 9.036064147949219e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 34.04042458534241s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.021753787994384766s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0008487701416015625s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 4.363059997558594e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 7.3909759521484375e-06s
INFO | --- Analysis for Bioportal_link took 211.57927417755127s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.5658400058746338s
Availability | VoID file availability check for BioSamples RDF took 0.0896153450012207s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 55.23031139373779s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02285909652709961s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0010581016540527344s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 6.29425048828125e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.2159347534179688e-05s
INFO | --- Analysis for biosamples-rdf took 407.6433484554291s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.11612629890441895s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0003509521484375s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.3621368408203125s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.022454500198364258s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0009591579437255859s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.0001423358917236328s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.4066696166992188e-05s
INFO | --- Analysis for bis-linked-data took 397.57765913009644s
Availability | SPARQL endpoint availability check for Bitzi took 8.726119995117188e-05s
Availability | VoID file availability check for Bitzi took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Bitzi took 0.28616833686828613s
Reputation | Calculation of the PageRank for Bitzi took 0.024358749389648438s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0011911392211914062s
Interlinking | Calculation of Clustering coefficient for Bitzi took 6.437301635742188e-05s
Believability | Calculation of trust value for Bitzi took 1.1205673217773438e-05s
INFO | --- Analysis for bitzi took 62.153627157211304s
Availability | SPARQL endpoint availability check for BizkaiSense took 0.22773003578186035s
Availability | VoID file availability check for BizkaiSense took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.4278995990753174s
Reputation | Calculation of the PageRank for BizkaiSense took 0.0228271484375s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.0517578125e-05s
Believability | Calculation of trust value for BizkaiSense took 1.2636184692382812e-05s
INFO | --- Analysis for bizkaisense took 63.83695721626282s
Availability | SPARQL endpoint availability check for blabla.itemlist took 9.083747863769531e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0008699893951416016s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.33954620361328125s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.022939682006835938s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.9802322387695312e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.1920928955078125e-05s
INFO | --- Analysis for blabla-itemlist took 32.161137342453s
Availability | SPARQL endpoint availability check for blabla.itemlist took 9.059906005859375e-05s
Availability | VoID file availability check for blabla.itemlist took 0.000965118408203125s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 60.065200090408325s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.7670135498046875e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.2159347534179688e-05s
INFO | --- Analysis for blabla_itemlist took 212.34614968299866s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.00010561943054199219s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 60.33385396003723s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.022526979446411133s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.001051187515258789s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 6.031990051269531e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for bll-thesaurus took 63.071799993515015s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.0913548469543457s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.31183505058288574s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.794929504394531e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for bluk-bnb took 11.270044326782227s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.20568108558654785s
Availability | VoID file availability check for Thesaurus BNCF took 0.0007977485656738281s
Extra | Recovery of all triples for Thesaurus BNCF took 46.5668888092041s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6115014553070068s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6907296180725098s
Interoperability | New terms check for Thesaurus BNCF took 1.7470827102661133s
Versatility | Languages check for Thesaurus BNCF took 6.32279896736145s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8644571304321289s
Security | Check HTTPS for Thesaurus BNCF took 0.10257649421691895s
Interpretability | RDF structures check for Thesaurus BNCF took 0.15549612045288086s
Versatility | Serialization formats check for Thesaurus BNCF took 0.11637616157531738s
Availability | RDF dump link check for Thesaurus BNCF took 0.11752462387084961s
License | MR license check for Thesaurus BNCF took 0.10631704330444336s
License | HR license check for Thesaurus BNCF took 0.17851591110229492s
Amount of data | Number of property check for Thesaurus BNCF took 0.12166690826416016s
Understandability | Number of label check for Thesaurus BNCF took 0.2959117889404297s
Understandability | URI regex check for Thesaurus BNCF took 0.4069347381591797s
Understandability | Vocabs check for Thesaurus BNCF took 0.11266160011291504s
Verifiability | Authors check for Thesaurus BNCF took 0.1201324462890625s
Verifiability | Publishers check for Thesaurus BNCF took 0.35463666915893555s
Performance | Throughput check for Thesaurus BNCF took 11.739855766296387s
Amount of data | Check the number of entities for Thesaurus BNCF took 8.893013000488281e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.11961007118225098s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12362360954284668s
Interlinking | skos check for Thesaurus BNCF took 1.2609889507293701s
Interlinking | skos check for Thesaurus BNCF took 0.1372983455657959s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.11605310440063477s
Currency | Creation date check for Thesaurus BNCF took 0.11236023902893066s
Currency | Modification date check for Thesaurus BNCF took 0.8952012062072754s
Rep.Conc. | URIs length for Thesaurus BNCF took 26.106406211853027s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.1251237392425537s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.11997771263122559s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1239156723022461s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 13.187772035598755s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4931657314300537s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.978375196456909s
Consistency | Disjoint class check for Thesaurus BNCF took 0.11060786247253418s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8089690208435059s
Consistency | Misplaced classes for Thesaurus BNCF took 6.91642689704895s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 6.9836719036102295s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.5421948432922363s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.2967138290405273s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.5470130443573s
Security | Sign check for Thesaurus BNCF took 0.15436244010925293s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.728878021240234s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 60.576334953308105s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.021255016326904297s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 8.392333984375e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.9073486328125e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.1920928955078125e-05s
INFO | --- Analysis for bncf-ns took 488.219003200531s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6800003051757812s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0005116462707519531s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9821925163269043s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3667397499084473s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.386685848236084s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.21697473526001s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.45200228691101s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31318140029907227s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3353149890899658s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.41959333419799805s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4297819137573242s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4865281581878662s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47037649154663086s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.49000000953674s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4290885925292969s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36142849922180176s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8397829532623291s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5022225379943848s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9106085300445557s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8473770618438721s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.745410680770874s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00010395050048828125s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5953545570373535s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34300947189331055s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2635345458984375s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2850213050842285s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5799126625061035s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0626049041748047s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4397733211517334s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.964603185653687s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4695866107940674s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0377960205078125s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03261423110961914s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030236005783081055s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37779879570007324s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.711775541305542s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5401511192321777s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.6456358432769775s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.766054630279541s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.828880548477173s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.032791852951049805s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5078654289245605s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4790785312652588s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.199377298355103s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 120.28337216377258s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.022141695022583008s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0012052059173583984s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.7697296142578125e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.1457672119140625e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3113021850585938e-05s
INFO | --- Analysis for bpr took 930.0873250961304s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.654594421386719e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.3234279155731201s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.023925065994262695s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.001796722412109375s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 0.00011348724365234375s
Believability | Calculation of trust value for Brazilian Politicians took 5.4836273193359375e-06s
INFO | --- Analysis for brazilian-politicians took 181.91973614692688s
Availability | SPARQL endpoint availability check for BrazilianCities took 254.8093602657318s
Availability | VoID file availability check for BrazilianCities took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.3310506343841553s
Reputation | Calculation of the PageRank for BrazilianCities took 0.021624088287353516s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 4.029273986816406e-05s
Believability | Calculation of trust value for BrazilianCities took 1.2636184692382812e-05s
INFO | --- Analysis for braziliancities took 631.1153717041016s
Availability | SPARQL endpoint availability check for Bricklink took 4.545389175415039s
Availability | VoID file availability check for Bricklink took 0.0009403228759765625s
Completeness | Calculation of interlinking completeness for Bricklink took 0.35152554512023926s
Reputation | Calculation of the PageRank for Bricklink took 0.034734249114990234s
Interlinking | Calculation of Degree of Connection for Bricklink took 6.008148193359375e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0020122528076171875s
Interlinking | Calculation of Clustering coefficient for Bricklink took 0.00019049644470214844s
Believability | Calculation of trust value for Bricklink took 1.3589859008789062e-05s
INFO | --- Analysis for bricklink took 324.29527401924133s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.041231632232666s
Availability | VoID file availability check for British Museum Collection took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for British Museum Collection took 60.64485764503479s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02094244956970215s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.504753112792969e-05s
Believability | Calculation of trust value for British Museum Collection took 1.2636184692382812e-05s
INFO | --- Analysis for british-museum-collection took 172.17491340637207s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 9.059906005859375e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 59.80060362815857s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02146434783935547s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 5.269050598144531e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.239776611328125e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 183.52259159088135s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 55.0724835395813s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0007472038269042969s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.42230725288391113s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.025710105895996094s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0012085437774658203s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 5.269050598144531e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.239776611328125e-05s
INFO | --- Analysis for bsv took 231.1651473045349s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 8.988380432128906e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.3343186378479004s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.02559375762939453s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0013353824615478516s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 4.6253204345703125e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.2636184692382812e-05s
INFO | --- Analysis for bund-offener-haushalt took 2.052455425262451s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 0.032289743423461914s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.41456031799316406s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.02157115936279297s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.0994415283203125e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 9.059906005859375e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 3.9601168632507324s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.2438366413116455s
Availability | VoID file availability check for business.data.gov.uk took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 1.0298981666564941s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.021077632904052734s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 6.461143493652344e-05s
Believability | Calculation of trust value for business.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for business-data-gov-uk took 3.581695795059204s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.4391052722930908s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0007309913635253906s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.351987600326538s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.448753833770752s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.3887650966644287s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.6871867179870605s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 41.17633295059204s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.2988746166229248s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.17373919486999512s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.3240952491760254s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.317535400390625s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2951226234436035s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.34062957763671875s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 11.757614612579346s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.35096192359924316s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.32099032402038574s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.568986177444458s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.29982852935791016s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3974111080169678s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.35393762588500977s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.91289472579956s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 8.869171142578125e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.27909350395202637s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.30697035789489746s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3104879856109619s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.30333781242370605s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.2880516052246094s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.45762014389038086s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.3157529830932617s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.893366098403931s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.30962562561035156s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.39514636993408203s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.3764955997467041s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.882925033569336s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03139162063598633s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.029114484786987305s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.4032280445098877s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.3926172256469727s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.3822455406188965s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.742678642272949s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2794744968414307s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.4399771690368652s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03772163391113281s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.33761048316955566s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.2922396659851074s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1496.1484870910645s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 4.699779510498047s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021314620971679688s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.2928924560546875e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.1920928955078125e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.0251998901367188e-05s
INFO | --- Analysis for BVMC took 1711.3412330150604s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 0.00011587142944335938s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 2.8410465717315674s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.021320343017578125s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.457069396972656e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 8.821487426757812e-06s
INFO | --- Analysis for cabbage took 28.64388370513916s
Availability | SPARQL endpoint availability check for cablegate took 1.6934916973114014s
Availability | VoID file availability check for cablegate took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for cablegate took 0.41323375701904297s
Reputation | Calculation of the PageRank for cablegate took 0.02331995964050293s
Interlinking | Calculation of Degree of Connection for cablegate took 1.52587890625e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0011909008026123047s
Interlinking | Calculation of Clustering coefficient for cablegate took 9.036064147949219e-05s
Believability | Calculation of trust value for cablegate took 1.239776611328125e-05s
INFO | --- Analysis for cablegate took 21.91668200492859s
Availability | SPARQL endpoint availability check for Calames took 8.749961853027344e-05s
Availability | VoID file availability check for Calames took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for Calames took 0.374861478805542s
Reputation | Calculation of the PageRank for Calames took 0.021089792251586914s
Interlinking | Calculation of Degree of Connection for Calames took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Calames took 0.0008504390716552734s
Interlinking | Calculation of Clustering coefficient for Calames took 4.1484832763671875e-05s
Believability | Calculation of trust value for Calames took 1.1205673217773438e-05s
INFO | --- Analysis for calames took 30.40379023551941s
Availability | SPARQL endpoint availability check for CaLiGraph took 30.115174531936646s
Availability | VoID file availability check for CaLiGraph took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for CaLiGraph took 3.4197075366973877s
Reputation | Calculation of the PageRank for CaLiGraph took 0.022473573684692383s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.170967102050781e-05s
Believability | Calculation of trust value for CaLiGraph took 1.3113021850585938e-05s
INFO | --- Analysis for CaLiGraph took 40.50513553619385s
Availability | SPARQL endpoint availability check for CaLiGraph took 30.19206953048706s
Availability | VoID file availability check for CaLiGraph took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.591799259185791s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021496057510375977s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.677078247070312e-05s
Believability | Calculation of trust value for CaLiGraph took 8.344650268554688e-06s
INFO | --- Analysis for caligraph took 61.132322549819946s
Availability | SPARQL endpoint availability check for can-link took 0.7112021446228027s
Availability | VoID file availability check for can-link took 0.2511475086212158s
Completeness | Calculation of interlinking completeness for can-link took 0.8144080638885498s
Reputation | Calculation of the PageRank for can-link took 0.022176742553710938s
Interlinking | Calculation of Degree of Connection for can-link took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for can-link took 0.0010874271392822266s
Interlinking | Calculation of Clustering coefficient for can-link took 4.124641418457031e-05s
Believability | Calculation of trust value for can-link took 1.0013580322265625e-05s
INFO | --- Analysis for can-link took 16.28237509727478s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07051229476928711s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 1.03352952003479s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.022014141082763672s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.3828277587890625e-05s
INFO | --- Analysis for cap-italy-rdf took 6.996203899383545s
Availability | SPARQL endpoint availability check for person took 9.584426879882812e-05s
Availability | VoID file availability check for person took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for person took 3.134077787399292s
Reputation | Calculation of the PageRank for person took 0.023044347763061523s
Interlinking | Calculation of Degree of Connection for person took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for person took 0.0010199546813964844s
Interlinking | Calculation of Clustering coefficient for person took 4.6253204345703125e-05s
Believability | Calculation of trust value for person took 1.4066696166992188e-05s
INFO | --- Analysis for card took 10.540950298309326s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.58306884765625e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 4.212827920913696s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02512812614440918s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0012440681457519531s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 5.2928924560546875e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.2874603271484375e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 6.5202436447143555s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 0.3988473415374756s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.46146535873413086s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.24249267578125e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.2874603271484375e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 9.034843683242798s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.6549441814422607s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00030732154846191406s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 116.03087615966797s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9975461959838867s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.65539836883545s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.193936586380005s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.21341347694397s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.0571534633636475s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.26835036277770996s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 0.5934696197509766s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.33724474906921387s
License | MR license check for Norway catch records dataset @PSNC took 0.6822981834411621s
License | HR license check for Norway catch records dataset @PSNC took 300.1698250770569s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.20574522018432617s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.827883005142212s
Understandability | URI regex check for Norway catch records dataset @PSNC took 1.413017988204956s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.5205812454223633s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.21482014656066895s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 2.9323441982269287s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.37743091583252s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 9.512901306152344e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.20087862014770508s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.18243074417114258s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4826083183288574s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4122183322906494s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 0.7932941913604736s
Currency | Creation date check for Norway catch records dataset @PSNC took 1.1602859497070312s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.2889440059661865s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 147.7788200378418s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.20548009872436523s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.39661431312561035s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.4093508720397949s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 40.42488980293274s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.7101340293884277s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.7093894481658936s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.2143266201019287s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 85.96117162704468s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.916621685028076s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 41.23949933052063s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.418623685836792s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 87.14108228683472s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 3.0460386276245117s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5341169834136963s
Security | Sign check for Norway catch records dataset @PSNC took 1.3257911205291748s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 8.953269243240356s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.6232867240905762s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.022129297256469727s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2276.205276966095s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 6.031990051269531e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.3271768093109131s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.02177572250366211s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00012636184692382812s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2159347534179688e-05s
INFO | --- Analysis for ce4r took 35.46529483795166s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4898545742034912s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0006237030029296875s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.2419533729553223s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7937419414520264s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3032379150390625s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.787193775177002s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.143465995788574s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23288488388061523s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.36070966720581055s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15282583236694336s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17343783378601074s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2915017604827881s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3880336284637451s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17721962928771973s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3568437099456787s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3136301040649414s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1732797622680664s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.29950618743896484s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23408102989196777s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.917662858963013s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 4.0531158447265625e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26758432388305664s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.291973352432251s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.9668810367584229s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1857900619506836s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1726224422454834s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6407716274261475s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2110762596130371s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.324521064758301s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23745250701904297s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2968134880065918s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.3296492099761963s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6276416778564453s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.03043961524963379s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02964186668395996s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5153017044067383s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 0.6295309066772461s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.8362929821014404s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.2819032669067383s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.654411792755127s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.030308246612548828s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.19487667083740234s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28007936477661133s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2520.770758867264s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.5774378776550293s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.02243518829345703s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0008206367492675781s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 5.9604644775390625e-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 1.3113021850585938e-05s
INFO | --- Analysis for ceo took 2667.706557035446s
Availability | SPARQL endpoint availability check for Charging Stations took 9.131431579589844e-05s
Availability | VoID file availability check for Charging Stations took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.3473052978515625s
Reputation | Calculation of the PageRank for Charging Stations took 0.022164106369018555s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.266334533691406e-05s
Believability | Calculation of trust value for Charging Stations took 1.1205673217773438e-05s
INFO | --- Analysis for charging-stations took 2.3828728199005127s
Availability | SPARQL endpoint availability check for Chat Game corpus took 0.00013256072998046875s
Availability | VoID file availability check for Chat Game corpus took 0.0007653236389160156s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.3281569480895996s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02255558967590332s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.5762786865234375e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.239776611328125e-05s
INFO | --- Analysis for chat-game-corpus took 11.97140908241272s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 2.2445731163024902s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.3224062919616699s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.023189544677734375s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.4332275390625e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 1.2159347534179688e-05s
INFO | --- Analysis for chebi took 4.448145151138306s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 8.7738037109375e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.7476158142089844s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02283763885498047s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0012564659118652344s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 8.535385131835938e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.1682510375976562e-05s
INFO | --- Analysis for chem2bio2rdf took 132.4260630607605s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.4326622486114502s
Availability | VoID file availability check for ChEMBL RDF took 0.09821343421936035s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.3299534320831299s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.021226882934570312s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.839897155761719e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.1920928955078125e-05s
INFO | --- Analysis for chembl-rdf took 3.588701009750366s
Availability | SPARQL endpoint availability check for chemdb  dataset took 2.32194447517395s
Availability | VoID file availability check for chemdb  dataset took 0.00037550926208496094s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.330488920211792s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.025485754013061523s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0013763904571533203s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 0.000102996826171875s
Believability | Calculation of trust value for chemdb  dataset took 1.239776611328125e-05s
INFO | --- Analysis for chemdb-basicInfo took 6.112598657608032s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 2.8086488246917725s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.5588037967681885s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02156662940979004s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.410743713378906e-05s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.2159347534179688e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 5.313340902328491s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 2.241610050201416s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 1.3837778568267822s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.023856401443481445s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0012445449829101562s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.888938903808594e-05s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.1920928955078125e-05s
INFO | --- Analysis for chemdb-phaseTransition took 5.852206468582153s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 11.177201986312866s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.34655046463012695s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02142024040222168s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.198883056640625e-05s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.1920928955078125e-05s
INFO | --- Analysis for chemdb-thermochemistry took 13.47858214378357s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 8.916854858398438e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.4280514717102051s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02403736114501953s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0012221336364746094s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.6716461181640625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.239776611328125e-05s
INFO | --- Analysis for chempedia-rdf took 8.609176635742188s
Availability | SPARQL endpoint availability check for Chiman Maru took 0.00011229515075683594s
Availability | VoID file availability check for Chiman Maru took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.6152524948120117s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02157306671142578s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.0279159545898438e-05s
Believability | Calculation of trust value for Chiman Maru took 1.1920928955078125e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 4.610057353973389s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.5285530090332s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.43447399139404297s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.022614240646362305s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0010352134704589844s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.673004150390625e-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 528.8026340007782s
Availability | SPARQL endpoint availability check for Chronicling America took 9.894371032714844e-05s
Availability | VoID file availability check for Chronicling America took 0.0007808208465576172s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.8589506149291992s
Reputation | Calculation of the PageRank for Chronicling America took 0.02246570587158203s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0009965896606445312s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00013065338134765625s
Believability | Calculation of trust value for Chronicling America took 1.2159347534179688e-05s
INFO | --- Analysis for chronicling-america took 246.10943603515625s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.5085201263427734s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0005998611450195312s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 81.93719410896301s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.5014009475708008s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.3999319076538086s
Interoperability | New terms check for Cultural Heritage Thesaurus took 1.8783211708068848s
Versatility | Languages check for Cultural Heritage Thesaurus took 6.015904903411865s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.140582799911499s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.33831214904785156s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.2805910110473633s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.140711307525635s
License | MR license check for Cultural Heritage Thesaurus took 0.32169294357299805s
License | HR license check for Cultural Heritage Thesaurus took 0.5496253967285156s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.32024645805358887s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3828773498535156s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5765328407287598s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.28032445907592773s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.45866847038269043s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.2824079990386963s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.59038519859314s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 9.012222290039062e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2987990379333496s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.3051607608795166s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3285713195800781s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.35164546966552734s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2846710681915283s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.9118132591247559s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.8116433620452881s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 28.63055992126465s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.041414737701416s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3372776508331299s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.29320454597473145s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.32916879653930664s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 7.072641849517822s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22284722328186035s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3476569652557373s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.8938415050506592s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.30517148971557617s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 7.215636491775513s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 3.3676273822784424s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00015115737915039062s
Security | Sign check for Cultural Heritage Thesaurus took 0.3334038257598877s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 378.8570439815521s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.6147351264953613s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.042203664779663086s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0008251667022705078s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00017547607421875s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.6586236953735352s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.4781951904296875e-05s
INFO | --- Analysis for cht took 619.7238240242004s
Availability | SPARQL endpoint availability check for ciard-ring took 8.726119995117188e-05s
Availability | VoID file availability check for ciard-ring took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.30468130111694336s
Reputation | Calculation of the PageRank for ciard-ring took 0.020929813385009766s
Interlinking | Calculation of Degree of Connection for ciard-ring took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.458427429199219e-05s
Believability | Calculation of trust value for ciard-ring took 7.867813110351562e-06s
INFO | --- Analysis for ciard-ring took 3.241783618927002s
Availability | SPARQL endpoint availability check for Cine Figure took 8.96453857421875e-05s
Availability | VoID file availability check for Cine Figure took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.3254203796386719s
Reputation | Calculation of the PageRank for Cine Figure took 0.021184921264648438s
Interlinking | Calculation of Degree of Connection for Cine Figure took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.4345855712890625e-05s
Believability | Calculation of trust value for Cine Figure took 1.1920928955078125e-05s
INFO | --- Analysis for Cine_Figure took 2.629735231399536s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 30.212596893310547s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.581291913986206s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.022055864334106445s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 6.723403930664062e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.33514404296875e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 155.03661465644836s
Availability | SPARQL endpoint availability check for CIPFA took 9.036064147949219e-05s
Availability | VoID file availability check for CIPFA took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for CIPFA took 0.30162882804870605s
Reputation | Calculation of the PageRank for CIPFA took 0.021310806274414062s
Interlinking | Calculation of Degree of Connection for CIPFA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.528594970703125e-05s
Believability | Calculation of trust value for CIPFA took 9.059906005859375e-06s
INFO | --- Analysis for cipfa took 1.8638572692871094s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 1.4342687129974365s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.321533203125s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.021251201629638672s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.00084686279296875s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00040984153747558594s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.2159347534179688e-05s
INFO | --- Analysis for ckan took 7.377145767211914s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6203970909118652s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5615360736846924s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.02315545082092285s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for CLaSSES took 6.895279407501221s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.3392181396484375e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 1.6990172863006592s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.022209882736206055s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.0517578125e-05s
Believability | Calculation of trust value for Temples of the Classical World took 9.059906005859375e-06s
INFO | --- Analysis for classical_temples took 9.641729831695557s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.116819143295288s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.6586339473724365s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.021298646926879883s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0010235309600830078s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 0.00010442733764648438s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 1.0251998901367188e-05s
INFO | --- Analysis for clean-energy-data-reegle took 5.362805604934692s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.988380432128906e-05s
Availability | VoID file availability check for CLLD-afbo took 0.5299086570739746s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.3260340690612793s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02118229866027832s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-afbo took 3.337860107421875e-06s
Believability | Calculation of trust value for CLLD-afbo took 1.2159347534179688e-05s
INFO | --- Analysis for clld-afbo took 5.733774662017822s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.7738037109375e-05s
Availability | VoID file availability check for CLLD-APICS took 0.46512842178344727s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 1.309037208557129s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.021141529083251953s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.891654968261719e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-APICS took 1.9073486328125e-06s
Believability | Calculation of trust value for CLLD-APICS took 1.0013580322265625e-05s
INFO | --- Analysis for clld-apics took 4.690370082855225s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 5.7697296142578125e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.7653329372406006s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.34525036811828613s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-EWAVE took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-EWAVE took 1.239776611328125e-05s
INFO | --- Analysis for clld-ewave took 5.975886106491089s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 9.584426879882812e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.5038208961486816s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.6030786037445068s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.021155595779418945s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for CLLD-GLOTTOLOG took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.2874603271484375e-05s
INFO | --- Analysis for clld-glottolog took 4.612903118133545s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.797645568847656e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.4823317527770996s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.8711018562316895s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.024393558502197266s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0012166500091552734s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 0.00010251998901367188s
Interoperability | Check the re-using of existing vocabs for CLLD-PHOIBLE took 2.6226043701171875e-06s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.3589859008789062e-05s
INFO | --- Analysis for clld-phoible took 9.83523678779602s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 9.703636169433594e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.4785125255584717s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.3042004108428955s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.915496826171875e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-SAILS took 2.6226043701171875e-06s
Believability | Calculation of trust value for CLLD-SAILS took 1.2636184692382812e-05s
INFO | --- Analysis for clld-sails took 3.6908442974090576s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-WALS took 0.4726123809814453s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.32931089401245117s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02240920066833496s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.320808410644531e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WALS took 2.6226043701171875e-06s
Believability | Calculation of trust value for CLLD-WALS took 1.2874603271484375e-05s
INFO | --- Analysis for clld-wals took 6.203304052352905s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 9.441375732421875e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.47120070457458496s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.3435397148132324s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02108168601989746s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.034706115722656e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WOLD took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-WOLD took 1.3113021850585938e-05s
INFO | --- Analysis for clld-wold took 6.010918617248535s
Availability | SPARQL endpoint availability check for COD inventory took 0.23216986656188965s
Availability | VoID file availability check for COD inventory took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for COD inventory took 0.32281064987182617s
Reputation | Calculation of the PageRank for COD inventory took 0.022562742233276367s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.552436828613281e-05s
Believability | Calculation of trust value for COD inventory took 1.2159347534179688e-05s
INFO | --- Analysis for cod-inventory took 2.706892251968384s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.13397574424743652s
Availability | VoID file availability check for Cooperation Databank took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.761650562286377s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02234673500061035s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 5.3882598876953125e-05s
Believability | Calculation of trust value for Cooperation Databank took 7.152557373046875e-06s
INFO | --- Analysis for CoDa took 3.4146173000335693s
Availability | SPARQL endpoint availability check for CODE Endpoint took 261.1051025390625s
Availability | VoID file availability check for CODE Endpoint took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.36612772941589355s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.02154707908630371s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 4.3392181396484375e-05s
Believability | Calculation of trust value for CODE Endpoint took 1.2159347534179688e-05s
INFO | --- Analysis for code-endpoint took 394.1543951034546s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.9260909557342529s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.4853336811065674s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02825140953063965s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.001348257064819336s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 4.482269287109375e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 8.58306884765625e-06s
INFO | --- Analysis for coins-openuplabs took 8.603554010391235s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.1996021270751953s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 3.0079715251922607s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.082389831542969e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.239776611328125e-05s
INFO | --- Analysis for CoLChina_sp2000 took 8.275355339050293s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.057622432708740234s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.8393728733062744s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.022124052047729492s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.792213439941406e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.3113021850585938e-05s
INFO | --- Analysis for colinda took 4.6608312129974365s
Availability | SPARQL endpoint availability check for CN  2012 took 25.908427715301514s
Availability | VoID file availability check for CN  2012 took 0.0008568763732910156s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.3522195816040039s
Reputation | Calculation of the PageRank for CN  2012 took 0.02138805389404297s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.57763671875e-05s
Believability | Calculation of trust value for CN  2012 took 9.059906005859375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 102.26980829238892s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 3.056166172027588s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0008215904235839844s
Extra | Recovery of all triples for Comments on Literature in Literature (CoLiL) took 134.9237413406372s
Performance | Total latancy measurement for Comments on Literature in Literature (CoLiL) took 8.138592004776001s
Amount of data | Number of triples check for Comments on Literature in Literature (CoLiL) took 145.40791773796082s
Interoperability | New terms check for Comments on Literature in Literature (CoLiL) took 128.77974891662598s
Versatility | Languages check for Comments on Literature in Literature (CoLiL) took 301.4125370979309s
Interpretability | Number of blank nodes check for Comments on Literature in Literature (CoLiL) took 194.82678055763245s
Security | Check HTTPS for Comments on Literature in Literature (CoLiL) took 1.097238302230835s
Interpretability | RDF structures check for Comments on Literature in Literature (CoLiL) took 2.3053958415985107s
Versatility | Serialization formats check for Comments on Literature in Literature (CoLiL) took 1.6417100429534912s
Availability | RDF dump link check for Comments on Literature in Literature (CoLiL) took 1.7305784225463867s
License | MR license check for Comments on Literature in Literature (CoLiL) took 1.6682682037353516s
License | HR license check for Comments on Literature in Literature (CoLiL) took 1.7245385646820068s
Amount of data | Number of property check for Comments on Literature in Literature (CoLiL) took 1.6693878173828125s
Understandability | Number of label check for Comments on Literature in Literature (CoLiL) took 1.9006586074829102s
Understandability | URI regex check for Comments on Literature in Literature (CoLiL) took 3.341430425643921s
Understandability | Vocabs check for Comments on Literature in Literature (CoLiL) took 1.706974983215332s
Verifiability | Authors check for Comments on Literature in Literature (CoLiL) took 1.706974983215332s
Verifiability | Publishers check for Comments on Literature in Literature (CoLiL) took 1.7058427333831787s
Performance | Throughput check for Comments on Literature in Literature (CoLiL) took 16.278708457946777s
Amount of data | Check the number of entities for Comments on Literature in Literature (CoLiL) took 9.250640869140625e-05s
Verifiability | Contribs. check for Comments on Literature in Literature (CoLiL) took 1.677076816558838s
Interlinking | sameAs chians check for Comments on Literature in Literature (CoLiL) took 1.7156240940093994s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 1.9386415481567383s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 1.8073585033416748s
Timeliness | dataset update frequency check for Comments on Literature in Literature (CoLiL) took 1.64695143699646s
Currency | Creation date check for Comments on Literature in Literature (CoLiL) took 1.6512031555175781s
Currency | Modification date check for Comments on Literature in Literature (CoLiL) took 1.6362712383270264s
Rep.Conc. | URIs length for Comments on Literature in Literature (CoLiL) took 471.10264110565186s
Interoperability | New vocabularies check for Comments on Literature in Literature (CoLiL) took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Comments on Literature in Literature (CoLiL) took 1.6721301078796387s
Accuracy | Check Functional Property for Comments on Literature in Literature (CoLiL) took 1.6590917110443115s
Accuracy | Check Inverse Functional Property for Comments on Literature in Literature (CoLiL) took 1.6885426044464111s
Accuracy | Check Empty annotation labels for Comments on Literature in Literature (CoLiL) took 2.117269515991211s
Accuracy | Check White space in annotation for Comments on Literature in Literature (CoLiL) took 0.0009732246398925781s
Accuracy | Check Datatype consistency for Comments on Literature in Literature (CoLiL) took 2.761720657348633s
Consistency | Disjoint class check for Comments on Literature in Literature (CoLiL) took 1.6769843101501465s
Consistency | Check Misplaced properties for Comments on Literature in Literature (CoLiL) took 303.1320779323578s
Consistency | Misplaced classes for Comments on Literature in Literature (CoLiL) took 10.470848560333252s
Consistency | Check Ontology hijacking for Comments on Literature in Literature (CoLiL) took 35.94664478302002s
Consistency | Check Invalid usage of undefined classes for Comments on Literature in Literature (CoLiL) took 1.2747421264648438s
Consistency | Check Invalid usage of undefined properties for Comments on Literature in Literature (CoLiL) took 303.5268454551697s
Conciseness | Check Extensional conciseness for Comments on Literature in Literature (CoLiL) took 3.003229856491089s
Conciseness | Check Intensional conciseness for Comments on Literature in Literature (CoLiL) took 2.2341549396514893s
Security | Sign check for Comments on Literature in Literature (CoLiL) took 2.300386667251587s
Availability | Check URIs Dereferenciability for Comments on Literature in Literature (CoLiL) took 17.23606777191162s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 120.26416516304016s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.023647308349609375s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for Comments on Literature in Literature (CoLiL) took 1.430511474609375e-06s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 1.5974044799804688e-05s
INFO | --- Analysis for comments-on-literature-in-literature took 3922.459928750992s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 0.00010204315185546875s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.31385207176208496s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02200770378112793s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0008287429809570312s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.361701965332031e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 1.239776611328125e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 57.89306688308716s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 6.842613220214844e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00040531158447265625s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.29755473136901855s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.021570444107055664s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.409385681152344e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 1.1920928955078125e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 14.453078031539917s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 0.00012302398681640625s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0003638267517089844s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.34271955490112305s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.023664236068725586s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.8848648071289062e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 1.0728836059570312e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 53.545355558395386s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 8.749961853027344e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.29930734634399414s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02333354949951172s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0012726783752441406s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 4.172325134277344e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 1.1920928955078125e-05s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 31.63336706161499s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.5808780193328857s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.38324689865112305s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.0234377384185791s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0012695789337158203s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.935264587402344e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for CompHistSem took 6.116168260574341s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 0.20208430290222168s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.589022159576416s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.024974584579467773s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0013675689697265625s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 5.1021575927734375e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.239776611328125e-05s
INFO | --- Analysis for comsode-d3-2 took 6.168741464614868s
Availability | SPARQL endpoint availability check for ConceptNet took 8.702278137207031e-05s
Availability | VoID file availability check for ConceptNet took 0.0008077621459960938s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.3160281181335449s
Reputation | Calculation of the PageRank for ConceptNet took 0.021129846572875977s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.0040740966796875e-05s
Believability | Calculation of trust value for ConceptNet took 1.049041748046875e-05s
INFO | --- Analysis for conceptnet took 12.363243818283081s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 9.012222290039062e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0003933906555175781s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 1.903806447982788s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.021182537078857422s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.20159912109375e-05s
Believability | Calculation of trust value for 2011 US Congress People took 7.152557373046875e-06s
INFO | --- Analysis for congresspeople took 6.627692222595215s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 1.6439263820648193s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0007712841033935547s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.3065650463104248s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.022329330444335938s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.765655517578125e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for connectivity-of-lod-datasets took 30.435829401016235s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.10287809371948242s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.32791590690612793s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.8371810913085938e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.2159347534179688e-05s
INFO | --- Analysis for copac-library-catalogue took 1.8945667743682861s
Availability | SPARQL endpoint availability check for Copyright Free Music took 9.298324584960938e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.560791015625s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.02366471290588379s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.6702880859375e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.2159347534179688e-05s
INFO | --- Analysis for Copyright_Free_Music took 5.460806608200073s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 9.131431579589844e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.567624568939209s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.021157026290893555s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.891654968261719e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.2159347534179688e-05s
INFO | --- Analysis for copyrighttermbank took 35.00226306915283s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.9114625453948975s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.3279075622558594s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.021031856536865234s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.886222839355469e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.1682510375976562e-05s
INFO | --- Analysis for core took 11.601147890090942s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.5447738170623779s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005931854248046875s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 110.68449091911316s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9942538738250732s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.445507764816284s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.291357278823853s
Versatility | Languages check for Corine linked dataset @PSNC took 300.21679973602295s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 1.9511640071868896s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.31974267959594727s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 0.7156736850738525s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.35282039642333984s
License | MR license check for Corine linked dataset @PSNC took 0.6318674087524414s
License | HR license check for Corine linked dataset @PSNC took 300.24154114723206s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.21149539947509766s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.2481908798217773s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.2946124076843262s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.5377216339111328s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.18658232688903809s
Verifiability | Publishers check for Corine linked dataset @PSNC took 2.9170982837677s
Performance | Throughput check for Corine linked dataset @PSNC took 11.021504402160645s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 8.916854858398438e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.1828899383544922s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.21025919914245605s
Interlinking | skos check for Corine linked dataset @PSNC took 0.5017483234405518s
Interlinking | skos check for Corine linked dataset @PSNC took 0.42499613761901855s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 0.7501883506774902s
Currency | Creation date check for Corine linked dataset @PSNC took 1.1529464721679688s
Currency | Modification date check for Corine linked dataset @PSNC took 0.2693207263946533s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 146.3275363445282s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.21499896049499512s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.4507880210876465s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.44312620162963867s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 38.42850089073181s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.730154514312744s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.6947410106658936s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.19875335693359375s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 86.15457606315613s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.719976902008057s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 30.86344838142395s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.406782627105713s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 87.40002202987671s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 3.0080182552337646s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.47034645080566406s
Security | Sign check for Corine linked dataset @PSNC took 1.3324270248413086s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 16.384042501449585s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.6913974285125732s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.02171635627746582s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for Corine_linked_dataset took 2253.1527235507965s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.988380432128906e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.3116109371185303s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02111530303955078s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.1948089599609375e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.1682510375976562e-05s
INFO | --- Analysis for corn took 107.49422287940979s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 9.822845458984375e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.6228010654449463s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.021235942840576172s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 2.9802322387695312e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 1.2636184692382812e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 59.962039947509766s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.6253204345703125e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.940103530883789s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.021393775939941406s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.6716461181640625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.1444091796875e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 37.01042127609253s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 9.036064147949219e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.32293701171875s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.023122310638427734s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0012996196746826172s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 7.987022399902344e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.1920928955078125e-05s
INFO | --- Analysis for cornetto took 15.232009887695312s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.19114327430725098s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0006425380706787109s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 226.77223944664001s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6055755615234375s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 45.15342974662781s
Interoperability | New terms check for Corporate Body Named Authority List  took 55.59322142601013s
Versatility | Languages check for Corporate Body Named Authority List  took 300.09085273742676s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 17.52874183654785s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.35202693939208984s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.45015692710876465s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 0.3310098648071289s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.175750732421875s
License | MR license check for Corporate Body Named Authority List  took 0.47104525566101074s
License | HR license check for Corporate Body Named Authority List  took 264.75208568573s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.9811384677886963s
Understandability | Number of label check for Corporate Body Named Authority List  took 3.306544542312622s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.4122469425201416s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.11431646347045898s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.3169822692871094s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.18259739875793457s
Performance | Throughput check for Corporate Body Named Authority List  took 10.540851354598999s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 0.0001285076141357422s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.14028334617614746s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 34.456963300704956s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3223388195037842s
Interlinking | skos check for Corporate Body Named Authority List  took 0.1753065586090088s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.20819783210754395s
Currency | Creation date check for Corporate Body Named Authority List  took 0.987739086151123s
Currency | Modification date check for Corporate Body Named Authority List  took 0.229400634765625s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 418.04572582244873s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.2121429443359375s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.20887541770935059s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.19408106803894043s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 43.46107053756714s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.1142332553863525s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.7791314125061035s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.1619861125946045s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 293.57854199409485s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.8562171459198s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 38.12233638763428s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.7051875591278076s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 293.74331545829773s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.275282382965088s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.39532470703125s
Security | Sign check for Corporate Body Named Authority List  took 0.24463558197021484s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 19.929684162139893s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.7497124671936035s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.021293163299560547s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.33514404296875e-05s
INFO | --- Analysis for corporate-body took 9840.616554498672s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5612831115722656s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 180.36429405212402s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.022341012954711914s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 6.341934204101562e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.9311904907226562e-05s
INFO | --- Analysis for CorpusFibonacci took 879.5704538822174s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.07730245590209961s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 179.8508656024933s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.02307915687561035s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.9577484130859375e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.7642974853515625e-05s
INFO | --- Analysis for corscheck took 277.1961920261383s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.19098806381225586s
Availability | VoID file availability check for Country Name Authority List took 0.0006690025329589844s
Extra | Recovery of all triples for Country Name Authority List took 162.7439112663269s
Performance | Total latancy measurement for Country Name Authority List took 0.5786914825439453s
Amount of data | Number of triples check for Country Name Authority List took 50.03481578826904s
Interoperability | New terms check for Country Name Authority List took 53.87265610694885s
Versatility | Languages check for Country Name Authority List took 300.1244649887085s
Interpretability | Number of blank nodes check for Country Name Authority List took 18.015519380569458s
Security | Check HTTPS for Country Name Authority List took 0.33045220375061035s
Interpretability | RDF structures check for Country Name Authority List took 0.2700839042663574s
Versatility | Serialization formats check for Country Name Authority List took 0.3283078670501709s
Availability | RDF dump link check for Country Name Authority List took 0.1835644245147705s
License | MR license check for Country Name Authority List took 0.48423218727111816s
License | HR license check for Country Name Authority List took 258.4180238246918s
Amount of data | Number of property check for Country Name Authority List took 0.17974495887756348s
Understandability | Number of label check for Country Name Authority List took 2.3561081886291504s
Understandability | URI regex check for Country Name Authority List took 0.36232686042785645s
Understandability | Vocabs check for Country Name Authority List took 0.11293292045593262s
Verifiability | Authors check for Country Name Authority List took 0.27512645721435547s
Verifiability | Publishers check for Country Name Authority List took 0.2480151653289795s
Performance | Throughput check for Country Name Authority List took 10.82954478263855s
Amount of data | Check the number of entities for Country Name Authority List took 0.00016951560974121094s
Verifiability | Contribs. check for Country Name Authority List took 0.14182114601135254s
Interlinking | sameAs chians check for Country Name Authority List took 6.321336507797241s
Interlinking | skos check for Country Name Authority List took 0.32201170921325684s
Interlinking | skos check for Country Name Authority List took 0.14189600944519043s
Timeliness | dataset update frequency check for Country Name Authority List took 0.21499013900756836s
Currency | Creation date check for Country Name Authority List took 1.1622731685638428s
Currency | Modification date check for Country Name Authority List took 0.20774102210998535s
Rep.Conc. | URIs length for Country Name Authority List took 395.2461681365967s
Interoperability | New vocabularies check for Country Name Authority List took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.17920184135437012s
Accuracy | Check Functional Property for Country Name Authority List took 0.22088074684143066s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.18212223052978516s
Accuracy | Check Empty annotation labels for Country Name Authority List took 40.154229164123535s
Accuracy | Check White space in annotation for Country Name Authority List took 3.098921775817871s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.7202208042144775s
Consistency | Disjoint class check for Country Name Authority List took 0.15097403526306152s
Consistency | Check Misplaced properties for Country Name Authority List took 292.243798494339s
Consistency | Misplaced classes for Country Name Authority List took 8.947601079940796s
Consistency | Check Ontology hijacking for Country Name Authority List took 40.116371631622314s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.7126808166503906s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 292.4699718952179s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.2850661277770996s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.31497693061828613s
Security | Sign check for Country Name Authority List took 0.3129701614379883s
Availability | Check URIs Dereferenciability for Country Name Authority List took 18.399197101593018s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 2.3935420513153076s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021897315979003906s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0010154247283935547s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.9073486328125e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.33514404296875e-05s
INFO | --- Analysis for country-authority-list took 9751.413657188416s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.0694117546081543s
Availability | VoID file availability check for Courts thesaurus took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 1.6769838333129883s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.081031799316406e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for courts-thesaurus took 6.2767016887664795s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.27382802963256836s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006940364837646484s
Extra | Recovery of all triples for Covid-on-the-Web Dataset took 2.1729815006256104s
Performance | Total latancy measurement for Covid-on-the-Web Dataset took 0.6090660095214844s
Amount of data | Number of triples check for Covid-on-the-Web Dataset took 47.99467849731445s
Interoperability | New terms check for Covid-on-the-Web Dataset took 8.880332231521606s
Versatility | Languages check for Covid-on-the-Web Dataset took 300.08935618400574s
Interpretability | Number of blank nodes check for Covid-on-the-Web Dataset took 70.96130537986755s
Interpretability | RDF structures check for Covid-on-the-Web Dataset took 0.18527555465698242s
Versatility | Serialization formats check for Covid-on-the-Web Dataset took 0.20174264907836914s
Availability | RDF dump link check for Covid-on-the-Web Dataset took 3.1468191146850586s
License | MR license check for Covid-on-the-Web Dataset took 0.31186389923095703s
License | HR license check for Covid-on-the-Web Dataset took 300.1778783798218s
Amount of data | Number of property check for Covid-on-the-Web Dataset took 0.1488499641418457s
Understandability | Number of label check for Covid-on-the-Web Dataset took 1.1653382778167725s
Understandability | URI regex check for Covid-on-the-Web Dataset took 0.40831851959228516s
Understandability | Vocabs check for Covid-on-the-Web Dataset took 0.1322917938232422s
Verifiability | Authors check for Covid-on-the-Web Dataset took 25.214606046676636s
Verifiability | Publishers check for Covid-on-the-Web Dataset took 0.6227843761444092s
Performance | Throughput check for Covid-on-the-Web Dataset took 10.529760837554932s
Amount of data | Check the number of entities for Covid-on-the-Web Dataset took 0.10400199890136719s
Verifiability | Contribs. check for Covid-on-the-Web Dataset took 0.28721189498901367s
Interlinking | sameAs chians check for Covid-on-the-Web Dataset took 0.12853622436523438s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.13471651077270508s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.12084436416625977s
Timeliness | dataset update frequency check for Covid-on-the-Web Dataset took 0.4418158531188965s
Currency | Creation date check for Covid-on-the-Web Dataset took 0.12821698188781738s
Currency | Modification date check for Covid-on-the-Web Dataset took 0.12272119522094727s
Rep.Conc. | URIs length for Covid-on-the-Web Dataset took 37.14471435546875s
Interoperability | New vocabularies check for Covid-on-the-Web Dataset took 85.39762926101685s
Consistency | Deprecated classes/propertiers check for Covid-on-the-Web Dataset took 0.11077427864074707s
Accuracy | Check Functional Property for Covid-on-the-Web Dataset took 0.35891270637512207s
Accuracy | Check Inverse Functional Property for Covid-on-the-Web Dataset took 0.3773670196533203s
Accuracy | Check Empty annotation labels for Covid-on-the-Web Dataset took 1.3630096912384033s
Accuracy | Check White space in annotation for Covid-on-the-Web Dataset took 0.060311317443847656s
Accuracy | Check Datatype consistency for Covid-on-the-Web Dataset took 0.09165573120117188s
Consistency | Disjoint class check for Covid-on-the-Web Dataset took 0.10898113250732422s
Consistency | Check Misplaced properties for Covid-on-the-Web Dataset took 47.22413206100464s
Consistency | Misplaced classes for Covid-on-the-Web Dataset took 1.3202552795410156s
Consistency | Check Ontology hijacking for Covid-on-the-Web Dataset took 2.135739326477051s
Consistency | Check Invalid usage of undefined classes for Covid-on-the-Web Dataset took 1.3399817943572998s
Consistency | Check Invalid usage of undefined properties for Covid-on-the-Web Dataset took 34.89635491371155s
Conciseness | Check Extensional conciseness for Covid-on-the-Web Dataset took 0.09676694869995117s
Conciseness | Check Intensional conciseness for Covid-on-the-Web Dataset took 1.314556360244751s
Security | Sign check for Covid-on-the-Web Dataset took 0.5040738582611084s
Availability | Check URIs Dereferenciability for Covid-on-the-Web Dataset took 14.091259002685547s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 1.1286370754241943s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.024457693099975586s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0012748241424560547s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 0.00012803077697753906s
Interoperability | Check the re-using of existing vocabs for Covid-on-the-Web Dataset took 92.05395150184631s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for Covid-on-the-Web took 8876.569880247116s
Availability | SPARQL endpoint availability check for CPA 2008 took 26.387972354888916s
Availability | VoID file availability check for CPA 2008 took 0.0008361339569091797s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.453047513961792s
Reputation | Calculation of the PageRank for CPA 2008 took 0.026557207107543945s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 5.340576171875e-05s
Believability | Calculation of trust value for CPA 2008 took 9.298324584960938e-06s
INFO | --- Analysis for cpa-2008 took 138.9498734474182s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.3382699489593506s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0006344318389892578s
Extra | Recovery of all triples for Cooperative Patent Classification took 20.893288612365723s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.6696183681488037s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.09920930862427s
Versatility | Languages check for Cooperative Patent Classification took 120.10707092285156s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.14219403266907s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.11788368225097656s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.11160397529602051s
Availability | RDF dump link check for Cooperative Patent Classification took 0.1225900650024414s
License | MR license check for Cooperative Patent Classification took 0.10948777198791504s
License | HR license check for Cooperative Patent Classification took 90.11600732803345s
Amount of data | Number of property check for Cooperative Patent Classification took 0.12823200225830078s
Understandability | Number of label check for Cooperative Patent Classification took 90.11374998092651s
Understandability | URI regex check for Cooperative Patent Classification took 0.23431777954101562s
Understandability | Vocabs check for Cooperative Patent Classification took 0.10056018829345703s
Verifiability | Authors check for Cooperative Patent Classification took 0.17241168022155762s
Verifiability | Publishers check for Cooperative Patent Classification took 0.12405586242675781s
Performance | Throughput check for Cooperative Patent Classification took 10.617739915847778s
Amount of data | Check the number of entities for Cooperative Patent Classification took 4.458427429199219e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.09705305099487305s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.1342780590057373s
Interlinking | skos check for Cooperative Patent Classification took 0.1276566982269287s
Interlinking | skos check for Cooperative Patent Classification took 0.11219501495361328s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.10902786254882812s
Currency | Creation date check for Cooperative Patent Classification took 0.12407231330871582s
Currency | Modification date check for Cooperative Patent Classification took 0.5670197010040283s
Rep.Conc. | URIs length for Cooperative Patent Classification took 147.84901356697083s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.15655827522277832s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 14.247822284698486s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.993011713027954s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.982803821563721s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.09685897827148438s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.23855829238892s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 16.703839778900146s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.5942554473876953s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.53698492050171s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 3.1102681159973145s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.16221237182617188s
Security | Sign check for Cooperative Patent Classification took 0.11562037467956543s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 0.9145064353942871s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.5932245254516602s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.022272109985351562s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0011637210845947266s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 2.1457672119140625e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.1444091796875e-05s
INFO | --- Analysis for CPC took 1307.5426194667816s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.108905792236328s
Availability | VoID file availability check for CPC 2008 took 0.0009548664093017578s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.31319475173950195s
Reputation | Calculation of the PageRank for CPC 2008 took 0.02152228355407715s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 5.3882598876953125e-05s
Believability | Calculation of trust value for CPC 2008 took 6.198883056640625e-06s
INFO | --- Analysis for cpc-2008 took 99.35187315940857s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.773401975631714s
Availability | VoID file availability check for CPV  2003 took 0.0008575916290283203s
Completeness | Calculation of interlinking completeness for CPV  2003 took 2.2302486896514893s
Reputation | Calculation of the PageRank for CPV  2003 took 0.021743059158325195s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.6716461181640625e-05s
Believability | Calculation of trust value for CPV  2003 took 9.5367431640625e-06s
INFO | --- Analysis for cpv-2003 took 99.31796002388s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.610600471496582s
Availability | VoID file availability check for CPV 2008 took 0.0009083747863769531s
Completeness | Calculation of interlinking completeness for CPV 2008 took 2.1396336555480957s
Reputation | Calculation of the PageRank for CPV 2008 took 0.022008895874023438s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0010068416595458984s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 6.389617919921875e-05s
Believability | Calculation of trust value for CPV 2008 took 1.0013580322265625e-05s
INFO | --- Analysis for cpv-2008 took 106.37233114242554s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.25719380378723s
Availability | VoID file availability check for crowdsourcing-fb took 0.0008969306945800781s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 7.651838064193726s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.022463321685791016s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 6.723403930664062e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.3828277587890625e-05s
INFO | --- Analysis for crowdsourcing-fb took 405.3793866634369s
Availability | SPARQL endpoint availability check for CRTM took 20.34310245513916s
Availability | VoID file availability check for CRTM took 0.0007812976837158203s
Completeness | Calculation of interlinking completeness for CRTM took 1.45487642288208s
Reputation | Calculation of the PageRank for CRTM took 0.021157264709472656s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0008225440979003906s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.695487976074219e-05s
Believability | Calculation of trust value for CRTM took 1.2159347534179688e-05s
INFO | --- Analysis for crtm took 46.71718716621399s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 1.1027772426605225s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.43477869033813477s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.027776479721069336s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0015163421630859375s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 6.246566772460938e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 1.2874603271484375e-05s
INFO | --- Analysis for crystal-eye took 10.74528169631958s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.922306299209595s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 1.8372411727905273s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02122783660888672s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 7.200241088867188e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.0013580322265625e-05s
INFO | --- Analysis for ctic-public-dataset took 53.32176637649536s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 8.511543273925781e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.6277642250061035s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020991086959838867s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.9087066650390625e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 1.0967254638671875e-05s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 46.12913799285889s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.3961648941040039s
Availability | VoID file availability check for CulturaLinkedData took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 16.96013116836548s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.790855407714844e-05s
Believability | Calculation of trust value for CulturaLinkedData took 1.5020370483398438e-05s
INFO | --- Analysis for culturalinkeddata took 41.05990195274353s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.19254326820373535s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 45.30426049232483s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.022133827209472656s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.839897155761719e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 1.2159347534179688e-05s
INFO | --- Analysis for cz-ares-or took 197.7352912425995s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11754369735717773s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.33837437629699707s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.021818161010742188s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0010044574737548828s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.267692565917969e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.1205673217773438e-05s
INFO | --- Analysis for cz-ares-rzp took 1.964005947113037s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11308860778808594s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 59.40374159812927s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.023778438568115234s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.001157999038696289s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 4.506111145019531e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.3113021850585938e-05s
INFO | --- Analysis for cz-cenia-irz-chemicals took 61.23760724067688s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.11258912086486816s
Availability | VoID file availability check for Integrated pollution registry took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.441878080368042s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.021837234497070312s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.001005411148071289s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 5.173683166503906e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.2874603271484375e-05s
INFO | --- Analysis for cz-cenia-pollution took 61.779505252838135s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11349105834960938s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.001394033432006836s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.31667351722717285s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.6716461181640625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 7.62939453125e-06s
INFO | --- Analysis for cz-contracts took 121.59282684326172s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.673004150390625e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 113.01325225830078s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.02415180206298828s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 1.7642974853515625e-05s
INFO | --- Analysis for cz-courts took 712.8210096359253s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.1292431354522705s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0009016990661621094s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.3770134449005127s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 4.38690185546875e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-bans took 189.74103546142578s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10944724082946777s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0007655620574951172s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 15.683922290802002s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.021758556365966797s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 5.14984130859375e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.5367431640625e-06s
INFO | --- Analysis for cz-ctia-confiscations took 274.0180823802948s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11658358573913574s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.3095371723175049s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.022904157638549805s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.314018249511719e-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.602503538131714s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.11646771430969238s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.45235514640808105s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.021100282669067383s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 3.910064697265625e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.415531635284424s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.10945415496826172s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.002437591552734375s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2993052005767822s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.409385681152344e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.245208740234375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 9.361112594604492s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.17500710487365723s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.31452488899230957s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.024369239807128906s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0012364387512207031s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 5.030632019042969e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 1.049041748046875e-05s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.634160041809082s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11301946640014648s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.33488941192626953s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02219104766845703s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.457069396972656e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 9.298324584960938e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.991424322128296s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.5467987060546875s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.3168673515319824s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.0271298885345459s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0013051033020019531s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 5.125999450683594e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-average-salaries took 2.756695032119751s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.38193249702453613s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 2.061163902282715s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02404499053955078s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0010662078857421875s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.8160552978515625e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 4.821845293045044s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3389418125152588s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3016016483306885s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.022151947021484375s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0008816719055175781s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.673004150390625e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0728836059570312e-05s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 2.610201358795166s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3558192253112793s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.5642123222351074s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.024475574493408203s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0013082027435302734s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 5.269050598144531e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 1.0251998901367188e-05s
INFO | --- Analysis for cz-czso-job-applicants took 2.849027156829834s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3737192153930664s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.4931528568267822s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.021356821060180664s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 2.864311695098877s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3582172393798828s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3355104923248291s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.022706270217895508s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0010945796966552734s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 4.839897155761719e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 8.58306884765625e-06s
INFO | --- Analysis for cz-czso-regions took 2.9943408966064453s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.34804248809814453s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.301851749420166s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.021897315979003906s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0008561611175537109s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.315376281738281e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 4.553794860839844e-05s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 2.945269823074341s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.3714127540588379s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2973973751068115s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.021705150604248047s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.933906555175781e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 1.0728836059570312e-05s
INFO | --- Analysis for cz-czso-social-service-facilities took 2.5351662635803223s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.36437058448791504s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.3319969177246094s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.02251148223876953s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0009765625s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.8160552978515625e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 2.545006275177002s
Availability | SPARQL endpoint availability check for ATC groups took 0.11731910705566406s
Availability | VoID file availability check for ATC groups took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for ATC groups took 0.4615015983581543s
Reputation | Calculation of the PageRank for ATC groups took 0.022977828979492188s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.001020669937133789s
Interlinking | Calculation of Clustering coefficient for ATC groups took 8.988380432128906e-05s
Believability | Calculation of trust value for ATC groups took 1.1682510375976562e-05s
INFO | --- Analysis for cz-eh-1-atc took 2.4400463104248047s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.11151289939880371s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.31372809410095215s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.021382570266723633s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.62396240234375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0013580322265625e-05s
INFO | --- Analysis for cz-fulfillments took 2.5742483139038086s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.03379535675048828s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0003743171691894531s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.3042259216308594s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.021802186965942383s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0009660720825195312s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 5.888938903808594e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 9.298324584960938e-06s
INFO | --- Analysis for cz-ic took 2.4694037437438965s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.13998651504516602s
Availability | VoID file availability check for List of Czech data boxes took 0.28089427947998047s
Extra | Recovery of all triples for List of Czech data boxes took 142.06675481796265s
Performance | Total latancy measurement for List of Czech data boxes took 0.5591628551483154s
Amount of data | Number of triples check for List of Czech data boxes took 9.518792629241943s
Interoperability | New terms check for List of Czech data boxes took 10.344162225723267s
Versatility | Languages check for List of Czech data boxes took 300.1418867111206s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.5653324127197266s
Interpretability | RDF structures check for List of Czech data boxes took 0.15606379508972168s
Versatility | Serialization formats check for List of Czech data boxes took 0.12421083450317383s
Availability | RDF dump link check for List of Czech data boxes took 15.009752750396729s
License | MR license check for List of Czech data boxes took 0.4386134147644043s
License | HR license check for List of Czech data boxes took 52.28090572357178s
Amount of data | Number of property check for List of Czech data boxes took 0.12485313415527344s
Understandability | Number of label check for List of Czech data boxes took 1.5814244747161865s
Understandability | URI regex check for List of Czech data boxes took 0.6189768314361572s
Understandability | Vocabs check for List of Czech data boxes took 0.12088131904602051s
Verifiability | Authors check for List of Czech data boxes took 5.236849546432495s
Verifiability | Publishers check for List of Czech data boxes took 0.8679492473602295s
Performance | Throughput check for List of Czech data boxes took 10.60356616973877s
Amount of data | Check the number of entities for List of Czech data boxes took 3.1514694690704346s
Verifiability | Contribs. check for List of Czech data boxes took 0.13985371589660645s
Interlinking | sameAs chians check for List of Czech data boxes took 0.2944159507751465s
Interlinking | skos check for List of Czech data boxes took 0.1890714168548584s
Interlinking | skos check for List of Czech data boxes took 0.10634732246398926s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.2233116626739502s
Currency | Creation date check for List of Czech data boxes took 0.2004694938659668s
Currency | Modification date check for List of Czech data boxes took 0.14441490173339844s
Rep.Conc. | URIs length for List of Czech data boxes took 109.81262230873108s
Interoperability | New vocabularies check for List of Czech data boxes took 31.61527705192566s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.37810444831848145s
Accuracy | Check Functional Property for List of Czech data boxes took 0.21906280517578125s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.19919466972351074s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 30.239128589630127s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.090301036834717s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.6631557941436768s
Consistency | Disjoint class check for List of Czech data boxes took 0.1360456943511963s
Consistency | Check Misplaced properties for List of Czech data boxes took 65.58859133720398s
Consistency | Misplaced classes for List of Czech data boxes took 7.88490629196167s
Consistency | Check Ontology hijacking for List of Czech data boxes took 32.293680906295776s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.4299352169036865s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 60.44263458251953s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.8620660305023193s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.3786759376525879s
Security | Sign check for List of Czech data boxes took 0.1406536102294922s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 382.89758563041687s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 2.120842218399048s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.023206472396850586s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0010826587677001953s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 20.78607988357544s
Believability | Calculation of trust value for List of Czech data boxes took 9.5367431640625e-06s
INFO | --- Analysis for cz-list-of-databoxes took 2070.485132217407s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13173294067382812s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2507791519165039s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 141.23549795150757s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5938832759857178s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.034698724746704s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.72938871383667s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.17356848716736s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.2739672660827637s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1392672061920166s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13022828102111816s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.727927207946777s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7410595417022705s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 53.081162214279175s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12568449974060059s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.714219093322754s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5294177532196045s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13467717170715332s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.978906154632568s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7358007431030273s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.708960056304932s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.254593849182129s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13069367408752441s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3013451099395752s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.21527481079101562s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11557316780090332s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2841789722442627s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.19561409950256348s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13899493217468262s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 109.5201632976532s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 19.07920742034912s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3921053409576416s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.24583840370178223s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2428748607635498s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.852325916290283s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.110825777053833s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.8298611640930176s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12041544914245605s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 65.06247353553772s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.843670606613159s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.24004340171814s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.456035852432251s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 60.86206078529358s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0415844917297363s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.43598413467407227s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.158461332321167s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 376.65382170677185s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 180.14162731170654s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0234377384185791s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.283684253692627s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3828277587890625e-05s
INFO | --- Analysis for cz-nace took 2281.271019220352s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2958047389984131s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005800724029541016s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 377.924435377121s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8675277233123779s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3664743900299072s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.88383150100708s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 111.6622576713562s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.2387328147888184s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.4513494968414307s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3435945510864258s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4558730125427246s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.743920087814331s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0671377182006836s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18535232543945312s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5134716033935547s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.53141188621521s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2722640037536621s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.448228120803833s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3375868797302246s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.820050239562988s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.369850158691406e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.19508147239685059s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17232155799865723s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4780690670013428s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.171555757522583s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.31904029846191406s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4669351577758789s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2449665069580078s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 85.99676442146301s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15643620491027832s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.32872629165649414s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3041195869445801s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 72.89915919303894s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.582022190093994s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.7535765171051025s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.22692322731018066s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.134108066558838s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.743239402770996s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 73.23223972320557s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7566823959350586s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.2895267009735107s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.435492992401123s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.25242137908935547s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.9817976951599121s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1304.1191594600677s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.4282219409942627s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.02233266830444336s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.00014281272888183594s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.3589859008789062e-05s
INFO | --- Analysis for cz-nkod took 21945.09132885933s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.15197443962097168s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.3295421600341797s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.021199703216552734s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0008304119110107422s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 4.315376281738281e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 1.0013580322265625e-05s
INFO | --- Analysis for cz-orders took 4.6311140060424805s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.21453118324279785s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.27393031120300293s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 141.9318597316742s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.6262331008911133s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.309461832046509s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.722452402114868s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.15267419815063s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.4172234535217285s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.15651679039001465s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.15169763565063477s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 15.249112844467163s
License | MR license check for Institutions of public power of the Czech Republic took 0.5142760276794434s
License | HR license check for Institutions of public power of the Czech Republic took 54.35531830787659s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.14172053337097168s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.704887866973877s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.5733292102813721s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.13280820846557617s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 4.907281875610352s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.7421767711639404s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.64766526222229s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.095945358276367s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.12589812278747559s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.29912877082824707s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.19027376174926758s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11997127532958984s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.2505648136138916s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.1979823112487793s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.1349649429321289s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 108.7859263420105s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 23.693217277526855s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.38100576400756836s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.24448299407958984s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.2994976043701172s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 31.668757915496826s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0865182876586914s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.8058536052703857s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.14530611038208008s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 65.69891333580017s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.9364542961120605s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 30.61654043197632s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.27945876121521s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 61.547555446624756s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.9045486450195312s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.37664031982421875s
Security | Sign check for Institutions of public power of the Czech Republic took 0.1471540927886963s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 392.1528854370117s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 180.36092734336853s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021325111389160156s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.1975250244140625e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 17.536072731018066s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 1.3828277587890625e-05s
INFO | --- Analysis for cz-ovm took 2614.859431028366s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.11589479446411133s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.32326412200927734s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.022516727447509766s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-ovm-agendas took 3.193748950958252s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1798839569091797s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007035732269287109s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 44.0620596408844s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5779199600219727s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 12.061140298843384s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 17.487605571746826s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.18255615234375s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12289261817932129s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5917432308197021s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12235116958618164s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8205997943878174s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11024713516235352s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11406612396240234s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11891913414001465s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7123041152954102s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2479102611541748s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14171385765075684s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.23796439170837402s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20675063133239746s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.646377563476562s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.821487426757812e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12142086029052734s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11908221244812012s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13670778274536133s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12000370025634766s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12222623825073242s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1336510181427002s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1358656883239746s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 118.99626588821411s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13237667083740234s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1378335952758789s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1409761905670166s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.955186367034912s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.268169403076172s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.686471462249756s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13367271423339844s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 83.59277415275574s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.69110894203186s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 15.006873607635498s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.4096183776855469s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 84.79209351539612s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.1245155334472656s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.284146785736084s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12335777282714844s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 1272.4656839370728s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.4794437885284424s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02371048927307129s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0017209053039550781s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.00014400482177734375s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.0994415283203125e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.33514404296875e-05s
INFO | --- Analysis for cz-ruian took 2091.2913773059845s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7376408576965332s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.3395233154296875s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.021071434020996094s
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.0008296966552734375s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 8.0108642578125e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-sao-audited-subjects took 3.2692275047302246s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.5122339725494385s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.9344556331634521s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.021290302276611328s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.00543212890625e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.8361475467681885s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4606196880340576s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 7.185173511505127s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020791053771972656s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.0994415283203125e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 1.0251998901367188e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 12.012357234954834s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10729551315307617s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.7120635509490967s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02272200584411621s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.001238107681274414s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 4.7206878662109375e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 16.98089098930359s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.11968302726745605s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.43375706672668457s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02533245086669922s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0013318061828613281s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 4.792213439941406e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.587221384048462s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11574029922485352s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 1.7819132804870605s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.023773670196533203s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0011448860168457031s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 5.14984130859375e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.2159347534179688e-05s
INFO | --- Analysis for cz-sidc-drugs took 6.264678716659546s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.18688201904296875s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006597042083740234s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 139.26801013946533s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.619081974029541s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.034035444259644s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.16427230834961s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1257076263428s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.448937177658081s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.15618491172790527s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.13874459266662598s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.944649696350098s
License | MR license check for Summary types of Czech institutions of public power took 0.7096645832061768s
License | HR license check for Summary types of Czech institutions of public power took 53.404810190200806s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.12364625930786133s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.8818318843841553s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.5882401466369629s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.1311643123626709s
Verifiability | Authors check for Summary types of Czech institutions of public power took 5.144342660903931s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.6885538101196289s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.477600574493408s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.2407169342041016s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.13249969482421875s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.2946789264678955s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.22142720222473145s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.12828636169433594s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.24985694885253906s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.23448419570922852s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.12816810607910156s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 110.56530857086182s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 16.815847635269165s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.4370732307434082s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.20459938049316406s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.19507169723510742s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 31.52191948890686s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.1163270473480225s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6971819400787354s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.14928174018859863s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 66.94409465789795s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 8.02353286743164s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 32.154704570770264s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.3874070644378662s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 59.99792456626892s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.8931801319122314s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.39208364486694336s
Security | Sign check for Summary types of Czech institutions of public power took 0.18540120124816895s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 392.1024389266968s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 179.6153061389923s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02135753631591797s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 5.125999450683594e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 21.843831300735474s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.2159347534179688e-05s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2583.7516417503357s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10564374923706055s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 120.13003301620483s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.021636009216308594s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 4.601478576660156e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 9.775161743164062e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 122.02503728866577s
Availability | SPARQL endpoint availability check for State funding providers took 0.11363458633422852s
Availability | VoID file availability check for State funding providers took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for State funding providers took 0.3268146514892578s
Reputation | Calculation of the PageRank for State funding providers took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.076957702636719e-05s
Believability | Calculation of trust value for State funding providers took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 75.11558675765991s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.13619542121887207s
Availability | VoID file availability check for Organizations active in R&D took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 2.8232271671295166s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020941734313964844s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.1484832763671875e-05s
Believability | Calculation of trust value for Organizations active in R&D took 1.2874603271484375e-05s
INFO | --- Analysis for cz-vavai-organizations took 28.84090495109558s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11635947227478027s
Availability | VoID file availability check for R&D Programmes took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.3134472370147705s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020876646041870117s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.172325134277344e-05s
Believability | Calculation of trust value for R&D Programmes took 9.298324584960938e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.3530004024505615s
Availability | SPARQL endpoint availability check for R&D Projects took 0.1130990982055664s
Availability | VoID file availability check for R&D Projects took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.3241264820098877s
Reputation | Calculation of the PageRank for R&D Projects took 0.03473544120788574s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0015943050384521484s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 6.890296936035156e-05s
Believability | Calculation of trust value for R&D Projects took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-projects took 2.8132736682891846s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10956549644470215s
Availability | VoID file availability check for Institutional research plans took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Institutional research plans took 1.6679754257202148s
Reputation | Calculation of the PageRank for Institutional research plans took 0.02545952796936035s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0009455680847167969s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.792213439941406e-05s
Believability | Calculation of trust value for Institutional research plans took 1.0013580322265625e-05s
INFO | --- Analysis for cz-vavai-research-plans took 4.188321828842163s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11632990837097168s
Availability | VoID file availability check for Results of R&D took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.31238627433776855s
Reputation | Calculation of the PageRank for Results of R&D took 0.02397465705871582s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.001275777816772461s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 5.364418029785156e-05s
Believability | Calculation of trust value for Results of R&D took 1.1444091796875e-05s
INFO | --- Analysis for cz-vavai-results took 2.4968297481536865s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.13581585884094238s
Availability | VoID file availability check for Tenders in R&D took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.29596424102783203s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.022668838500976562s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0008556842803955078s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 5.5789947509765625e-05s
Believability | Calculation of trust value for Tenders in R&D took 9.775161743164062e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.6579692363739014s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 8.96453857421875e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.3031344413757324s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.02114725112915039s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0010612010955810547s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 4.172325134277344e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.1682510375976562e-05s
INFO | --- Analysis for czech_addresses took 3.5238685607910156s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5669426918029785s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.00040602684020996094s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.5604612827301025s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.670424938201904s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3635404109954834s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0007183551788330078s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 138.55698084831238s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0072593688964844s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 3.6394433975219727s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.285965919494629s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.33288884162903s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.23546433448791504s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.1142725944519043s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.2626197338104248s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.22212815284729004s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.20120763778686523s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.2437288761138916s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.26885652542114s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2629890441894531s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 2.419583320617676s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 1.047576904296875s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.5048079490661621s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 41.22005748748779s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 139.23455142974854s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.480737686157227s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 9.202957153320312e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 61.080952882766724s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 1.0335569381713867s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.3793656826019287s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.4762439727783203s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.22399401664733887s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.3848896026611328s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.8838257789611816s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 94.56400442123413s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.23645329475402832s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.47832274436950684s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.427661657333374s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 46.97516870498657s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.267505168914795s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.7341794967651367s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.3887953758239746s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.30799412727356s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 7.911798477172852s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 55.48663544654846s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4032988548278809s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 22.975197076797485s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 3.0765268802642822s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.25052833557128906s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.23689842224121094s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 17.537662029266357s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 1.842026710510254s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02186441421508789s
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.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00017404556274414062s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 5.9604644775390625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.3589859008789062e-05s
INFO | --- Analysis for data-bnf-fr took 40212.05968117714s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.426072359085083s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.48148059844970703s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.32758355140686035s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02435159683227539s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0013210773468017578s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 9.846687316894531e-05s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 14.331298112869263s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 1.049041748046875e-05s
INFO | --- Analysis for data-cnr-it took 21.711766242980957s
Availability | SPARQL endpoint availability check for Data.gov took 1.6963670253753662s
Availability | VoID file availability check for Data.gov took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Data.gov took 3.1385247707366943s
Reputation | Calculation of the PageRank for Data.gov took 0.022241830825805664s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0011553764343261719s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.8623809814453125e-05s
Believability | Calculation of trust value for Data.gov took 1.0013580322265625e-05s
INFO | --- Analysis for data-gov took 22.94481897354126s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.03795623779296875s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 2.427245855331421s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.023047208786010742s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 8.130073547363281e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 1.0013580322265625e-05s
INFO | --- Analysis for data-gov-ie took 10.883443832397461s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.410743713378906e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 3.1155545711517334s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02432990074157715s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0012011528015136719s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 9.083747863769531e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 9.298324584960938e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 8.563891887664795s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 19.92629337310791s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 1.1054456233978271s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.022034883499145508s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0009665489196777344s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 8.344650268554688e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.1444091796875e-05s
INFO | --- Analysis for data-hnm-hu took 129.99399065971375s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.1390533447265625s
Availability | VoID file availability check for Climb Dataincubator took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.33104968070983887s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.748603820800781e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-climb took 3.721766471862793s
Availability | SPARQL endpoint availability check for Discogs in RDF took 8.845329284667969e-05s
Availability | VoID file availability check for Discogs in RDF took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.31052494049072266s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.021538972854614258s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.751319885253906e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-discogs took 4.440047264099121s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05000448226928711s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.5456807613372803s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.027863502502441406s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.00152587890625s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 8.654594421386719e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 9.059906005859375e-06s
INFO | --- Analysis for data-incubator-metoffice took 7.047373294830322s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.13678932189941406s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.40459179878234863s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.021427392959594727s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007469654083251953s
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.1682510375976562e-05s
INFO | --- Analysis for data-incubator-moseley took 6.3731420040130615s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05001401901245117s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.39222145080566406s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.021142005920410156s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 0.00010895729064941406s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.1682510375976562e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 6.066958427429199s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.4946720600128174s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.000579833984375s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 3.1423094272613525s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.021028518676757812s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 9.369850158691406e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 9.298324584960938e-06s
INFO | --- Analysis for data-incubator-nasa took 12.450997114181519s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.05365562438964844s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 3.4730560779571533s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.022014141082763672s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.724761962890625e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-our-airports took 14.852078676223755s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.059088706970214844s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 19.260120391845703s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02111339569091797s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.512901306152344e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-pokedex took 62.932289600372314s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.04388093948364258s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 20.315584421157837s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.022251367568969727s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.001104116439819336s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 0.0001246929168701172s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.2636184692382812e-05s
INFO | --- Analysis for data-incubator-smcjournals took 86.2123293876648s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.3671393394470215s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0005435943603515625s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 22.749156951904297s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.7390463352203369s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 19.08534526824951s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.4387116432189941s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.177907705307007s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.14347743988037s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.21341633796691895s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.5079567432403564s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.411639928817749s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.1903057098388672s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.20379066467285156s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.144415616989136s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 1.824676752090454s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.158762454986572s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 1.3340096473693848s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.59371018409729s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 10.636492490768433s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 1.4480111598968506s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.80264663696289s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 0.00015234947204589844s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 1.9883034229278564s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.8607091903686523s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.5541329383850098s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.24748015403747559s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.18233275413513184s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 3.3436105251312256s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 3.675590991973877s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 42.99174976348877s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 67.9447729587555s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.21974706649780273s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.19015073776245117s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.15751314163208008s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 30.097002267837524s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.034339666366577s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.255876064300537s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.8890085220336914s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 1.0402019023895264s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.49372911453247s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 8.719377040863037s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.3918023109436035s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.6263654232025146s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 3.087686061859131s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.35643863677978516s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.13857102394104004s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.06689715385437012s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 13.349616765975952s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.022069454193115234s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0010652542114257812s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 423.92904567718506s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.2874603271484375e-05s
INFO | --- Analysis for data-open-ac-uk took 1140.4000751972198s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7678813934326172s
Availability | VoID file availability check for Persée in RDF took 0.0006163120269775391s
Extra | Recovery of all triples for Persée in RDF took 1.1377038955688477s
Performance | Total latancy measurement for Persée in RDF took 0.6844539642333984s
Amount of data | Number of triples check for Persée in RDF took 0.8886575698852539s
Interoperability | New terms check for Persée in RDF took 1.8806538581848145s
Versatility | Languages check for Persée in RDF took 121.10034966468811s
Interpretability | Number of blank nodes check for Persée in RDF took 0.5247068405151367s
Interpretability | RDF structures check for Persée in RDF took 0.9495565891265869s
Versatility | Serialization formats check for Persée in RDF took 0.9930558204650879s
Availability | RDF dump link check for Persée in RDF took 0.33617687225341797s
License | MR license check for Persée in RDF took 2.001607894897461s
License | HR license check for Persée in RDF took 40.366437911987305s
Amount of data | Number of property check for Persée in RDF took 0.17482471466064453s
Understandability | Number of label check for Persée in RDF took 2.676950216293335s
Understandability | URI regex check for Persée in RDF took 1.1768467426300049s
Understandability | Vocabs check for Persée in RDF took 0.5584378242492676s
Verifiability | Authors check for Persée in RDF took 0.8519096374511719s
Verifiability | Publishers check for Persée in RDF took 0.5744810104370117s
Performance | Throughput check for Persée in RDF took 10.62238359451294s
Amount of data | Check the number of entities for Persée in RDF took 0.0005784034729003906s
Verifiability | Contribs. check for Persée in RDF took 0.4746379852294922s
Interlinking | sameAs chians check for Persée in RDF took 0.24279141426086426s
Interlinking | skos check for Persée in RDF took 0.9304170608520508s
Interlinking | skos check for Persée in RDF took 0.1326742172241211s
Timeliness | dataset update frequency check for Persée in RDF took 0.9207777976989746s
Currency | Creation date check for Persée in RDF took 0.5174059867858887s
Currency | Modification date check for Persée in RDF took 0.7858080863952637s
Rep.Conc. | URIs length for Persée in RDF took 3.5350182056427s
Interoperability | New vocabularies check for Persée in RDF took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.12970447540283203s
Accuracy | Check Functional Property for Persée in RDF took 0.16911649703979492s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.14971470832824707s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.510528564453125s
Accuracy | Check White space in annotation for Persée in RDF took 0.0381627082824707s
Accuracy | Check Datatype consistency for Persée in RDF took 0.029035329818725586s
Consistency | Disjoint class check for Persée in RDF took 0.3863861560821533s
Consistency | Check Misplaced properties for Persée in RDF took 2.628208875656128s
Consistency | Misplaced classes for Persée in RDF took 0.21217036247253418s
Consistency | Check Ontology hijacking for Persée in RDF took 1.767742395401001s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.3011491298675537s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.7705392837524414s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.0339052677154541s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.13246488571166992s
Security | Sign check for Persée in RDF took 1.1810925006866455s
Availability | Check URIs Dereferenciability for Persée in RDF took 1373.0595569610596s
Completeness | Calculation of interlinking completeness for Persée in RDF took 43.69125151634216s
Reputation | Calculation of the PageRank for Persée in RDF took 0.021462678909301758s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00012111663818359375s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 1.1920928955078125e-05s
INFO | --- Analysis for data-persee-fr took 1895.0159862041473s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 1.5203843116760254s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0004055500030517578s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 120.26172161102295s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.02229595184326172s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 3.075599670410156e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0011401176452636719s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 4.6253204345703125e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 1.2874603271484375e-05s
INFO | --- Analysis for data-southampton-ac-uk took 123.71864581108093s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.4505770206451416s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0003895759582519531s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 119.44269609451294s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.021574735641479492s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0008192062377929688s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.000133514404296875s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.3828277587890625e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 312.38289403915405s
Availability | SPARQL endpoint availability check for Open Data Web took 10.98618745803833s
Availability | VoID file availability check for Open Data Web took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for Open Data Web took 179.94437885284424s
Reputation | Calculation of the PageRank for Open Data Web took 0.02728271484375s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0010721683502197266s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 7.081031799316406e-05s
Believability | Calculation of trust value for Open Data Web took 1.0967254638671875e-05s
INFO | --- Analysis for data.odw.tw took 611.5295803546906s
Availability | SPARQL endpoint availability check for DataFAQs took 5.555152893066406e-05s
Availability | VoID file availability check for DataFAQs took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.5050663948059082s
Reputation | Calculation of the PageRank for DataFAQs took 0.021626949310302734s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.0994415283203125e-05s
Believability | Calculation of trust value for DataFAQs took 1.3113021850585938e-05s
INFO | --- Analysis for datafaqs took 91.67021131515503s
Availability | SPARQL endpoint availability check for datahub took 8.869171142578125e-05s
Availability | VoID file availability check for datahub took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for datahub took 0.32500791549682617s
Reputation | Calculation of the PageRank for datahub took 0.021556854248046875s
Interlinking | Calculation of Degree of Connection for datahub took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for datahub took 5.054473876953125e-05s
Believability | Calculation of trust value for datahub took 1.1682510375976562e-05s
INFO | --- Analysis for datahub took 5.926469564437866s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.844246864318848s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.5266354084014893s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.021064281463623047s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.1444091796875e-05s
INFO | --- Analysis for datahub-kr-datamap took 12.068418502807617s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3024585247039795s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3061861991882324s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.319450378417969e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.867813110351562e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 9.279045104980469s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.38108539581299s
Availability | VoID file availability check for datos-artium-org took 0.001176595687866211s
Completeness | Calculation of interlinking completeness for datos-artium-org took 6.836419105529785s
Reputation | Calculation of the PageRank for datos-artium-org took 0.03043985366821289s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.001211404800415039s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00013780593872070312s
Believability | Calculation of trust value for datos-artium-org took 1.3113021850585938e-05s
INFO | --- Analysis for datos-artium-org took 180.6685721874237s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8137476444244385s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006985664367675781s
Extra | Recovery of all triples for Datos.bcn.cl took 50.54518413543701s
Performance | Total latancy measurement for Datos.bcn.cl took 6.116547584533691s
Amount of data | Number of triples check for Datos.bcn.cl took 17.386189937591553s
Interoperability | New terms check for Datos.bcn.cl took 4.9546051025390625s
Versatility | Languages check for Datos.bcn.cl took 301.0379903316498s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.3514158725738525s
Security | Check HTTPS for Datos.bcn.cl took 0.716116189956665s
Interpretability | RDF structures check for Datos.bcn.cl took 1.4236736297607422s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2382490634918213s
Availability | RDF dump link check for Datos.bcn.cl took 1.2364096641540527s
License | MR license check for Datos.bcn.cl took 1.2460172176361084s
License | HR license check for Datos.bcn.cl took 271.5452208518982s
Amount of data | Number of property check for Datos.bcn.cl took 1.2769091129302979s
Understandability | Number of label check for Datos.bcn.cl took 2.2182705402374268s
Understandability | URI regex check for Datos.bcn.cl took 2.4267356395721436s
Understandability | Vocabs check for Datos.bcn.cl took 1.2066779136657715s
Verifiability | Authors check for Datos.bcn.cl took 1.2420926094055176s
Verifiability | Publishers check for Datos.bcn.cl took 1.2079110145568848s
Performance | Throughput check for Datos.bcn.cl took 12.24971342086792s
Amount of data | Check the number of entities for Datos.bcn.cl took 5.53131103515625e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.240316390991211s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2383642196655273s
Interlinking | skos check for Datos.bcn.cl took 1.224557638168335s
Interlinking | skos check for Datos.bcn.cl took 1.1946446895599365s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2388436794281006s
Currency | Creation date check for Datos.bcn.cl took 1.2330503463745117s
Currency | Modification date check for Datos.bcn.cl took 1.1992506980895996s
Rep.Conc. | URIs length for Datos.bcn.cl took 47.38270330429077s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.197502851486206s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.214808702468872s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.2238683700561523s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 29.254746913909912s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.34263181686401367s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.28212475776672363s
Consistency | Disjoint class check for Datos.bcn.cl took 1.2337369918823242s
Consistency | Check Misplaced properties for Datos.bcn.cl took 17.781328201293945s
Consistency | Misplaced classes for Datos.bcn.cl took 2.109177350997925s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 22.945722579956055s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.231475591659546s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 15.263934135437012s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.3239593505859375s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.5265858173370361s
Security | Sign check for Datos.bcn.cl took 1.2436716556549072s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7631.579370260239s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.1709775924682617s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02169036865234375s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.6689300537109375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 1.1444091796875e-05s
INFO | --- Analysis for datos-bcn-cl took 8833.64960193634s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.7287137508392334s
Availability | VoID file availability check for datos.bne.es took 0.0006685256958007812s
Extra | Recovery of all triples for datos.bne.es took 132.24652791023254s
Performance | Total latancy measurement for datos.bne.es took 1.4795246124267578s
Amount of data | Number of triples check for datos.bne.es took 0.923332691192627s
Interoperability | New terms check for datos.bne.es took 2.3427534103393555s
Versatility | Languages check for datos.bne.es took 60.85371160507202s
Interpretability | Number of blank nodes check for datos.bne.es took 0.3099842071533203s
Security | Check HTTPS for datos.bne.es took 0.18212080001831055s
Interpretability | RDF structures check for datos.bne.es took 0.6502091884613037s
Versatility | Serialization formats check for datos.bne.es took 0.4951043128967285s
Availability | RDF dump link check for datos.bne.es took 0.33934998512268066s
License | MR license check for datos.bne.es took 0.6470766067504883s
License | HR license check for datos.bne.es took 61.726518869400024s
Amount of data | Number of property check for datos.bne.es took 0.41475939750671387s
Understandability | Number of label check for datos.bne.es took 1.2520298957824707s
Understandability | URI regex check for datos.bne.es took 0.8055284023284912s
Understandability | Vocabs check for datos.bne.es took 0.35136866569519043s
Verifiability | Authors check for datos.bne.es took 0.4944179058074951s
Verifiability | Publishers check for datos.bne.es took 0.447955846786499s
Performance | Throughput check for datos.bne.es took 11.10182809829712s
Amount of data | Check the number of entities for datos.bne.es took 0.00010180473327636719s
Verifiability | Contribs. check for datos.bne.es took 0.6206226348876953s
Interlinking | sameAs chians check for datos.bne.es took 0.2969393730163574s
Interlinking | skos check for datos.bne.es took 0.6190791130065918s
Interlinking | skos check for datos.bne.es took 0.2701253890991211s
Timeliness | dataset update frequency check for datos.bne.es took 0.4645230770111084s
Currency | Creation date check for datos.bne.es took 0.4317290782928467s
Currency | Modification date check for datos.bne.es took 0.31488513946533203s
Rep.Conc. | URIs length for datos.bne.es took 54.44137978553772s
Interoperability | New vocabularies check for datos.bne.es took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.2982668876647949s
Accuracy | Check Functional Property for datos.bne.es took 0.29239630699157715s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.3241569995880127s
Accuracy | Check Empty annotation labels for datos.bne.es took 38.42808747291565s
Accuracy | Check White space in annotation for datos.bne.es took 1.630138635635376s
Accuracy | Check Datatype consistency for datos.bne.es took 1.3283872604370117s
Consistency | Disjoint class check for datos.bne.es took 0.328671932220459s
Consistency | Check Misplaced properties for datos.bne.es took 8.598871231079102s
Consistency | Misplaced classes for datos.bne.es took 4.475325584411621s
Consistency | Check Ontology hijacking for datos.bne.es took 43.67426300048828s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.2319905757904053s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 9.314724683761597s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.5120470523834229s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.292569637298584s
Security | Sign check for datos.bne.es took 1.0432538986206055s
Availability | Check URIs Dereferenciability for datos.bne.es took 10.274535179138184s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.37473130226135254s
Reputation | Calculation of the PageRank for datos.bne.es took 0.021667957305908203s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00012111663818359375s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 8.821487426757812e-06s
Believability | Calculation of trust value for datos.bne.es took 1.33514404296875e-05s
INFO | --- Analysis for datos-bne-es took 559.9723649024963s
Availability | SPARQL endpoint availability check for dbacademic took 0.06455421447753906s
Availability | VoID file availability check for dbacademic took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for dbacademic took 0.3899118900299072s
Reputation | Calculation of the PageRank for dbacademic took 0.02284550666809082s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.147125244140625e-05s
Believability | Calculation of trust value for dbacademic took 1.1444091796875e-05s
INFO | --- Analysis for dbacademic took 121.07110381126404s
Availability | SPARQL endpoint availability check for DBkWik took 0.21149182319641113s
Availability | VoID file availability check for DBkWik took 0.0006489753723144531s
Extra | Recovery of all triples for DBkWik took 1.5087225437164307s
Performance | Total latancy measurement for DBkWik took 0.49840712547302246s
Amount of data | Number of triples check for DBkWik took 4.037873029708862s
Interoperability | New terms check for DBkWik took 2.0615289211273193s
Versatility | Languages check for DBkWik took 60.346580266952515s
Interpretability | Number of blank nodes check for DBkWik took 0.1895911693572998s
Interpretability | RDF structures check for DBkWik took 0.2125396728515625s
Versatility | Serialization formats check for DBkWik took 0.18581151962280273s
Availability | RDF dump link check for DBkWik took 2.7136101722717285s
License | MR license check for DBkWik took 0.2572309970855713s
License | HR license check for DBkWik took 61.11908006668091s
Amount of data | Number of property check for DBkWik took 0.14432764053344727s
Understandability | Number of label check for DBkWik took 2.405536651611328s
Understandability | URI regex check for DBkWik took 0.2957286834716797s
Understandability | Vocabs check for DBkWik took 0.11609148979187012s
Verifiability | Authors check for DBkWik took 0.11488199234008789s
Verifiability | Publishers check for DBkWik took 0.09159064292907715s
Performance | Throughput check for DBkWik took 10.46390962600708s
Amount of data | Check the number of entities for DBkWik took 0.00019097328186035156s
Verifiability | Contribs. check for DBkWik took 0.10810542106628418s
Interlinking | sameAs chians check for DBkWik took 0.15908098220825195s
Interlinking | skos check for DBkWik took 0.48922038078308105s
Interlinking | skos check for DBkWik took 0.0944223403930664s
Timeliness | dataset update frequency check for DBkWik took 0.2326502799987793s
Currency | Creation date check for DBkWik took 0.268782377243042s
Currency | Modification date check for DBkWik took 0.11678504943847656s
Rep.Conc. | URIs length for DBkWik took 11.577737808227539s
Interoperability | New vocabularies check for DBkWik took 6.227349281311035s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.20225811004638672s
Accuracy | Check Functional Property for DBkWik took 0.30201196670532227s
Accuracy | Check Inverse Functional Property for DBkWik took 0.2689805030822754s
Accuracy | Check Empty annotation labels for DBkWik took 1.1884675025939941s
Accuracy | Check White space in annotation for DBkWik took 0.02392578125s
Accuracy | Check Datatype consistency for DBkWik took 0.03883194923400879s
Consistency | Disjoint class check for DBkWik took 0.13539958000183105s
Consistency | Check Misplaced properties for DBkWik took 11.821461915969849s
Consistency | Misplaced classes for DBkWik took 0.6087667942047119s
Consistency | Check Ontology hijacking for DBkWik took 1.7054004669189453s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.1621885299682617s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.684344053268433s
Conciseness | Check Extensional conciseness for DBkWik took 0.03418731689453125s
Conciseness | Check Intensional conciseness for DBkWik took 1.0021507740020752s
Security | Sign check for DBkWik took 0.2516670227050781s
Availability | Check URIs Dereferenciability for DBkWik took 11.797244310379028s
Completeness | Calculation of interlinking completeness for DBkWik took 180.34197878837585s
Reputation | Calculation of the PageRank for DBkWik took 0.02855062484741211s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0012950897216796875s
Interlinking | Calculation of Clustering coefficient for DBkWik took 0.00011277198791503906s
Interoperability | Check the re-using of existing vocabs for DBkWik took 3.839646100997925s
Believability | Calculation of trust value for DBkWik took 9.298324584960938e-06s
INFO | --- Analysis for dbkwik took 1815.695452451706s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 5.364418029785156e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 10.276219606399536s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.021445512771606445s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011658668518066406s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.33514404296875e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 312.9369282722473s
Availability | SPARQL endpoint availability check for dbnary took 0.28463315963745117s
Availability | VoID file availability check for dbnary took 0.0005676746368408203s
Extra | Recovery of all triples for dbnary took 1.020064353942871s
Performance | Total latancy measurement for dbnary took 0.42267489433288574s
Amount of data | Number of triples check for dbnary took 1.6684138774871826s
Interoperability | New terms check for dbnary took 3.4813740253448486s
Versatility | Languages check for dbnary took 60.98048114776611s
Interpretability | Number of blank nodes check for dbnary took 6.072179317474365s
Security | Check HTTPS for dbnary took 0.2161252498626709s
Interpretability | RDF structures check for dbnary took 0.16839313507080078s
Versatility | Serialization formats check for dbnary took 0.09771442413330078s
Availability | RDF dump link check for dbnary took 0.07150053977966309s
License | MR license check for dbnary took 0.3854410648345947s
License | HR license check for dbnary took 63.3563756942749s
Amount of data | Number of property check for dbnary took 0.10944461822509766s
Understandability | Number of label check for dbnary took 1.424328088760376s
Understandability | URI regex check for dbnary took 0.14078092575073242s
Understandability | Vocabs check for dbnary took 0.2564659118652344s
Verifiability | Authors check for dbnary took 0.6246204376220703s
Verifiability | Publishers check for dbnary took 0.1885993480682373s
Performance | Throughput check for dbnary took 10.418896198272705s
Amount of data | Check the number of entities for dbnary took 9.846687316894531e-05s
Verifiability | Contribs. check for dbnary took 0.2085115909576416s
Interlinking | sameAs chians check for dbnary took 0.09610557556152344s
Interlinking | skos check for dbnary took 0.33917665481567383s
Interlinking | skos check for dbnary took 0.09702420234680176s
Timeliness | dataset update frequency check for dbnary took 0.20679426193237305s
Currency | Creation date check for dbnary took 0.3041074275970459s
Currency | Modification date check for dbnary took 0.13555312156677246s
Rep.Conc. | URIs length for dbnary took 11.353057146072388s
Interoperability | New vocabularies check for dbnary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.10198807716369629s
Accuracy | Check Functional Property for dbnary took 0.2631044387817383s
Accuracy | Check Inverse Functional Property for dbnary took 0.1723341941833496s
Accuracy | Check Empty annotation labels for dbnary took 0.5682473182678223s
Accuracy | Check White space in annotation for dbnary took 0.025413036346435547s
Accuracy | Check Datatype consistency for dbnary took 0.028947830200195312s
Consistency | Disjoint class check for dbnary took 0.14667630195617676s
Consistency | Check Misplaced properties for dbnary took 8.91750979423523s
Consistency | Misplaced classes for dbnary took 0.24489712715148926s
Consistency | Check Ontology hijacking for dbnary took 1.5833096504211426s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.22316312789917s
Consistency | Check Invalid usage of undefined properties for dbnary took 9.871143102645874s
Conciseness | Check Extensional conciseness for dbnary took 0.03703880310058594s
Conciseness | Check Intensional conciseness for dbnary took 0.1902914047241211s
Security | Sign check for dbnary took 0.07317733764648438s
Availability | Check URIs Dereferenciability for dbnary took 11.025593519210815s
Completeness | Calculation of interlinking completeness for dbnary took 60.05726146697998s
Reputation | Calculation of the PageRank for dbnary took 0.02104473114013672s
Interlinking | Calculation of Degree of Connection for dbnary took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.8650970458984375e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.430511474609375e-06s
Believability | Calculation of trust value for dbnary took 1.6689300537109375e-05s
INFO | --- Analysis for dbnary took 850.5892155170441s
Availability | SPARQL endpoint availability check for DBpedia took 1.2526154518127441s
Availability | VoID file availability check for DBpedia took 0.8884737491607666s
Extra | Recovery of all triples for DBpedia took 5.228338003158569s
Performance | Total latancy measurement for DBpedia took 3.4741480350494385s
Amount of data | Number of triples check for DBpedia took 4.1042115688323975s
Interoperability | New terms check for DBpedia took 7.534609794616699s
Versatility | Languages check for DBpedia took 32.19918513298035s
Interpretability | Number of blank nodes check for DBpedia took 0.6937341690063477s
Security | Check HTTPS for DBpedia took 0.44132423400878906s
Interpretability | RDF structures check for DBpedia took 3.309760570526123s
Versatility | Serialization formats check for DBpedia took 0.707108736038208s
Availability | RDF dump link check for DBpedia took 0.7418973445892334s
License | MR license check for DBpedia took 5.53859543800354s
License | HR license check for DBpedia took 32.436230182647705s
Amount of data | Number of property check for DBpedia took 0.9796693325042725s
Understandability | Number of label check for DBpedia took 13.412384033203125s
Understandability | URI regex check for DBpedia took 1.5528624057769775s
Understandability | Vocabs check for DBpedia took 0.7980833053588867s
Verifiability | Authors check for DBpedia took 1.462299108505249s
Verifiability | Publishers check for DBpedia took 3.1541316509246826s
Performance | Throughput check for DBpedia took 13.893141984939575s
Amount of data | Check the number of entities for DBpedia took 3.910064697265625e-05s
Verifiability | Contribs. check for DBpedia took 0.787196159362793s
Interlinking | sameAs chians check for DBpedia took 1.7435047626495361s
Interlinking | skos check for DBpedia took 7.913394927978516s
Interlinking | skos check for DBpedia took 0.6765139102935791s
Timeliness | dataset update frequency check for DBpedia took 3.3962175846099854s
Currency | Creation date check for DBpedia took 0.8569154739379883s
Currency | Modification date check for DBpedia took 0.7820661067962646s
Rep.Conc. | URIs length for DBpedia took 37.93345618247986s
Interoperability | New vocabularies check for DBpedia took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.7269055843353271s
Accuracy | Check Functional Property for DBpedia took 0.8848369121551514s
Accuracy | Check Inverse Functional Property for DBpedia took 0.6910088062286377s
Accuracy | Check Empty annotation labels for DBpedia took 3.5690627098083496s
Accuracy | Check White space in annotation for DBpedia took 0.03022313117980957s
Accuracy | Check Datatype consistency for DBpedia took 0.028999805450439453s
Consistency | Disjoint class check for DBpedia took 1.6395704746246338s
Consistency | Check Misplaced properties for DBpedia took 33.890527963638306s
Consistency | Misplaced classes for DBpedia took 15.096954822540283s
Consistency | Check Ontology hijacking for DBpedia took 3.5309321880340576s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.1425080299377441s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.9613914489746094s
Conciseness | Check Extensional conciseness for DBpedia took 0.03476071357727051s
Conciseness | Check Intensional conciseness for DBpedia took 23.77498507499695s
Security | Sign check for DBpedia took 0.8379008769989014s
Availability | Check URIs Dereferenciability for DBpedia took 6137.990216493607s
Completeness | Calculation of interlinking completeness for DBpedia took 0.7900352478027344s
Reputation | Calculation of the PageRank for DBpedia took 0.02203202247619629s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009522438049316406s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia took 8973.827395439148s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 9.417533874511719e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0003662109375s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.3996727466583252s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.02147960662841797s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.915496826171875e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 8.175488233566284s
Availability | SPARQL endpoint availability check for DBpedia Commons took 5.444430828094482s
Availability | VoID file availability check for DBpedia Commons took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.30104994773864746s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.02344202995300293s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0012538433074951172s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 0.00011658668518066406s
Believability | Calculation of trust value for DBpedia Commons took 1.3828277587890625e-05s
INFO | --- Analysis for dbpedia-commons took 11.251445293426514s
Availability | SPARQL endpoint availability check for DBpedia in German took 384.2881348133087s
Availability | VoID file availability check for DBpedia in German took 0.0008337497711181641s
Completeness | Calculation of interlinking completeness for DBpedia in German took 7.9211626052856445s
Reputation | Calculation of the PageRank for DBpedia in German took 0.021220922470092773s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 7.796287536621094e-05s
Believability | Calculation of trust value for DBpedia in German took 1.1205673217773438e-05s
INFO | --- Analysis for dbpedia-de took 598.5337300300598s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 20.590482711791992s
Availability | VoID file availability check for DBpedia in Greek took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.34272265434265137s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02116227149963379s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00019884109497070312s
Believability | Calculation of trust value for DBpedia in Greek took 1.1682510375976562e-05s
INFO | --- Analysis for dbpedia-el took 387.73945593833923s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.4353957176208496s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006251335144042969s
Extra | Recovery of all triples for DBpedia in Spanish took 3.4593372344970703s
Performance | Total latancy measurement for DBpedia in Spanish took 1.2379486560821533s
Amount of data | Number of triples check for DBpedia in Spanish took 1.7130186557769775s
Interoperability | New terms check for DBpedia in Spanish took 2.7077035903930664s
Versatility | Languages check for DBpedia in Spanish took 60.98849868774414s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.3534352779388428s
Security | Check HTTPS for DBpedia in Spanish took 0.13742637634277344s
Interpretability | RDF structures check for DBpedia in Spanish took 1.1508378982543945s
Versatility | Serialization formats check for DBpedia in Spanish took 0.4061868190765381s
Availability | RDF dump link check for DBpedia in Spanish took 0.36439037322998047s
License | MR license check for DBpedia in Spanish took 0.6445481777191162s
License | HR license check for DBpedia in Spanish took 60.34711980819702s
Amount of data | Number of property check for DBpedia in Spanish took 0.30999755859375s
Understandability | Number of label check for DBpedia in Spanish took 1.1872000694274902s
Understandability | URI regex check for DBpedia in Spanish took 0.6975288391113281s
Understandability | Vocabs check for DBpedia in Spanish took 0.5940735340118408s
Verifiability | Authors check for DBpedia in Spanish took 0.2941935062408447s
Verifiability | Publishers check for DBpedia in Spanish took 0.3013889789581299s
Performance | Throughput check for DBpedia in Spanish took 11.420011043548584s
Amount of data | Check the number of entities for DBpedia in Spanish took 9.1552734375e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.28642892837524414s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.9941554069519043s
Interlinking | skos check for DBpedia in Spanish took 0.6126184463500977s
Interlinking | skos check for DBpedia in Spanish took 0.21709465980529785s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.41375207901000977s
Currency | Creation date check for DBpedia in Spanish took 0.33882808685302734s
Currency | Modification date check for DBpedia in Spanish took 0.29210996627807617s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.618396282196045s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.30637073516845703s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.4175572395324707s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.39708447456359863s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.522819995880127s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.031748294830322266s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.02955484390258789s
Consistency | Disjoint class check for DBpedia in Spanish took 0.29193639755249023s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.24564790725708s
Consistency | Misplaced classes for DBpedia in Spanish took 1.2148258686065674s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.323145866394043s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.1565678119659424s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.707198143005371s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.04092216491699219s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.708740234375s
Security | Sign check for DBpedia in Spanish took 0.31485867500305176s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 17.40439486503601s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 180.51702332496643s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.02159595489501953s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011563301086425781s
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 1.1682510375976562e-05s
INFO | --- Analysis for dbpedia-es took 1966.5321912765503s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2510545253753662s
Availability | VoID file availability check for DBpedia in Basque took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.3528721332550049s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02333998680114746s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0011849403381347656s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 4.1484832763671875e-05s
Believability | Calculation of trust value for DBpedia in Basque took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-eu took 7.03533673286438s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.13976311683654785s
Availability | VoID file availability check for DBpedia in French took 0.0006029605865478516s
Extra | Recovery of all triples for DBpedia in French took 82.18829250335693s
Performance | Total latancy measurement for DBpedia in French took 0.43837451934814453s
Amount of data | Number of triples check for DBpedia in French took 1.7928378582000732s
Interoperability | New terms check for DBpedia in French took 2.050839900970459s
Versatility | Languages check for DBpedia in French took 300.10061717033386s
Interpretability | Number of blank nodes check for DBpedia in French took 0.25237226486206055s
Security | Check HTTPS for DBpedia in French took 0.1820836067199707s
Interpretability | RDF structures check for DBpedia in French took 0.4515254497528076s
Versatility | Serialization formats check for DBpedia in French took 0.21790814399719238s
Availability | RDF dump link check for DBpedia in French took 6.68686318397522s
License | MR license check for DBpedia in French took 1.8893063068389893s
License | HR license check for DBpedia in French took 76.3142294883728s
Amount of data | Number of property check for DBpedia in French took 0.1835188865661621s
Understandability | Number of label check for DBpedia in French took 1.9184324741363525s
Understandability | URI regex check for DBpedia in French took 0.29151296615600586s
Understandability | Vocabs check for DBpedia in French took 0.17634367942810059s
Verifiability | Authors check for DBpedia in French took 0.405529260635376s
Verifiability | Publishers check for DBpedia in French took 0.3769373893737793s
Performance | Throughput check for DBpedia in French took 10.334228754043579s
Amount of data | Check the number of entities for DBpedia in French took 2.1453473567962646s
Verifiability | Contribs. check for DBpedia in French took 0.12616896629333496s
Interlinking | sameAs chians check for DBpedia in French took 0.2850761413574219s
Interlinking | skos check for DBpedia in French took 0.3390684127807617s
Interlinking | skos check for DBpedia in French took 0.08362603187561035s
Timeliness | dataset update frequency check for DBpedia in French took 0.5026698112487793s
Currency | Creation date check for DBpedia in French took 0.1487727165222168s
Currency | Modification date check for DBpedia in French took 0.13163423538208008s
Rep.Conc. | URIs length for DBpedia in French took 36.619733810424805s
Interoperability | New vocabularies check for DBpedia in French took 21.6910240650177s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.1171870231628418s
Accuracy | Check Functional Property for DBpedia in French took 0.13942480087280273s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.10829663276672363s
Accuracy | Check Empty annotation labels for DBpedia in French took 26.59233856201172s
Accuracy | Check White space in annotation for DBpedia in French took 3.0812675952911377s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6718475818634033s
Consistency | Disjoint class check for DBpedia in French took 0.21975946426391602s
Consistency | Check Misplaced properties for DBpedia in French took 7.709361791610718s
Consistency | Misplaced classes for DBpedia in French took 9.75485634803772s
Consistency | Check Ontology hijacking for DBpedia in French took 19.49722933769226s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.2237131595611572s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 8.49304747581482s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.1871306896209717s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.1873667240142822s
Security | Sign check for DBpedia in French took 0.13366127014160156s
Availability | Check URIs Dereferenciability for DBpedia in French took 2165.08882021904s
Completeness | Calculation of interlinking completeness for DBpedia in French took 1.5023109912872314s
Reputation | Calculation of the PageRank for DBpedia in French took 0.03191733360290527s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.0002086162567138672s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 13.275780200958252s
Believability | Calculation of trust value for DBpedia in French took 1.0967254638671875e-05s
INFO | --- Analysis for dbpedia-fr took 2987.8488924503326s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9277245998382568s
Availability | VoID file availability check for DBpedia in Japanese took 3.9774649143218994s
Extra | Recovery of all triples for DBpedia in Japanese took 5.552759408950806s
Performance | Total latancy measurement for DBpedia in Japanese took 6.615048170089722s
Amount of data | Number of triples check for DBpedia in Japanese took 54.49124455451965s
Interoperability | New terms check for DBpedia in Japanese took 17.445066213607788s
Versatility | Languages check for DBpedia in Japanese took 1.3394925594329834s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.337944746017456s
Security | Check HTTPS for DBpedia in Japanese took 0.8012640476226807s
Interpretability | RDF structures check for DBpedia in Japanese took 1.7189877033233643s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3437349796295166s
Availability | RDF dump link check for DBpedia in Japanese took 1.336705207824707s
License | MR license check for DBpedia in Japanese took 1.9667606353759766s
License | HR license check for DBpedia in Japanese took 121.31717109680176s
Amount of data | Number of property check for DBpedia in Japanese took 1.3323793411254883s
Understandability | Number of label check for DBpedia in Japanese took 22.998682022094727s
Understandability | URI regex check for DBpedia in Japanese took 2.667572259902954s
Understandability | Vocabs check for DBpedia in Japanese took 1.3353264331817627s
Verifiability | Authors check for DBpedia in Japanese took 1.3365075588226318s
Verifiability | Publishers check for DBpedia in Japanese took 2.9548842906951904s
Performance | Throughput check for DBpedia in Japanese took 13.30653715133667s
Amount of data | Check the number of entities for DBpedia in Japanese took 9.012222290039062e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3447039127349854s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.954995632171631s
Interlinking | skos check for DBpedia in Japanese took 1.3249971866607666s
Interlinking | skos check for DBpedia in Japanese took 2.1173007488250732s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.6329560279846191s
Currency | Creation date check for DBpedia in Japanese took 1.3637235164642334s
Currency | Modification date check for DBpedia in Japanese took 1.3368949890136719s
Rep.Conc. | URIs length for DBpedia in Japanese took 139.0445806980133s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3329460620880127s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3600103855133057s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3591561317443848s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.0464556217193604s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02634906768798828s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.02902388572692871s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4542882442474365s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.66231918334961s
Consistency | Misplaced classes for DBpedia in Japanese took 3.00276255607605s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.192731618881226s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2705771923065186s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.65841245651245s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.035741329193115234s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.2248661518096924s
Security | Sign check for DBpedia in Japanese took 1.3658692836761475s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 20.410133361816406s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.3734762668609619s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.021355628967285156s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010943412780761719s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-ja took 1247.027415752411s
Availability | SPARQL endpoint availability check for dbpedia lite took 9.632110595703125e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.3075368404388428s
Reputation | Calculation of the PageRank for dbpedia lite took 0.021831512451171875s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0008695125579833984s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00012230873107910156s
Believability | Calculation of trust value for dbpedia lite took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-lite took 366.1741874217987s
Availability | SPARQL endpoint availability check for DBpedia-Live took 2.4998536109924316s
Availability | VoID file availability check for DBpedia-Live took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.46361756324768066s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.02213597297668457s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.743171691894531e-05s
Believability | Calculation of trust value for DBpedia-Live took 1.1920928955078125e-05s
INFO | --- Analysis for dbpedia-live took 15.796517133712769s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2555580139160156s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.3406713008880615s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00018334388732910156s
Believability | Calculation of trust value for DBpedia in Dutch took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-nl took 2.9075517654418945s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 1.038128137588501s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.3238210678100586s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.153915405273438e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.1920928955078125e-05s
INFO | --- Analysis for dbpedia-pt took 4.2069926261901855s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 0.00013971328735351562s
Availability | VoID file availability check for DBpedia Spotlight took 0.0007653236389160156s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.513995885848999s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.021516799926757812s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.0994415283203125e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia-spotlight took 11.993610382080078s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 8.654594421386719e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.32279419898986816s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 7.414817810058594e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.523760080337524s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 0.2973294258117676s
Availability | VoID file availability check for DBpedia Wikidata took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.3358149528503418s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.022052526473999023s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.075599670410156e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 1.0967254638671875e-05s
INFO | --- Analysis for dbpedia-wikidata took 2.7699027061462402s
Availability | SPARQL endpoint availability check for DBpedia took 8.940696716308594e-05s
Availability | VoID file availability check for DBpedia took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for DBpedia took 0.4957726001739502s
Reputation | Calculation of the PageRank for DBpedia took 0.02246570587158203s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.0279159545898438e-05s
Believability | Calculation of trust value for DBpedia took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia_ took 2.970644474029541s
Availability | SPARQL endpoint availability check for DBTropes took 9.059906005859375e-05s
Availability | VoID file availability check for DBTropes took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for DBTropes took 0.8138978481292725s
Reputation | Calculation of the PageRank for DBTropes took 0.02142167091369629s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.369850158691406e-05s
Believability | Calculation of trust value for DBTropes took 1.239776611328125e-05s
INFO | --- Analysis for dbtropes took 2.996941328048706s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 9.036064147949219e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.6834805011749268s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.02257847785949707s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.001233816146850586s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 5.078315734863281e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 1.3828277587890625e-05s
INFO | --- Analysis for dbtune took 5.938229084014893s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 9.012222290039062e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.3254728317260742s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.02323174476623535s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.001092672348022461s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 6.961822509765625e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.4066696166992188e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 2.006950616836548s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 9.012222290039062e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.30142903327941895s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.021357297897338867s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.457069396972656e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.2874603271484375e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 2.1695642471313477s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.618880033493042s
Availability | VoID file availability check for DBTune.org/classical took 0.0011570453643798828s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.3262510299682617s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.0220639705657959s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.462501525878906e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.9550323486328125e-05s
INFO | --- Analysis for dbtune-classical took 8.019761800765991s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.778492212295532s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2991054058074951s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.022202730178833008s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.651878356933594e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.239776611328125e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 9.260092735290527s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 0.26749253273010254s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.3510572910308838s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.651878356933594e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.5497207641601562e-05s
INFO | --- Analysis for dbtune-magnatune took 3.178581953048706s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.3866457939148s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 15.121429204940796s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.027817726135253906s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.0001456737518310547s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-musicbrainz took 453.6113317012787s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.33800482749938965s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.4191877841949463s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.021001577377319336s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.3882598876953125e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.2159347534179688e-05s
INFO | --- Analysis for dbtune-myspace took 28.0715274810791s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 1.068206548690796s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 23.297343492507935s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.021003246307373047s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0008313655853271484s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.266334533691406e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 1.1682510375976562e-05s
INFO | --- Analysis for dclg-openuplabs took 59.04250693321228s
Availability | SPARQL endpoint availability check for data.dcs took 8.96453857421875e-05s
Availability | VoID file availability check for data.dcs took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for data.dcs took 0.3152015209197998s
Reputation | Calculation of the PageRank for data.dcs took 0.0239410400390625s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for data.dcs took 7.081031799316406e-05s
Believability | Calculation of trust value for data.dcs took 1.2874603271484375e-05s
INFO | --- Analysis for dcs-sheffield took 74.00797605514526s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.2472007274627686s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 34.34656381607056s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 5.626678466796875e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 2.1219253540039062e-05s
INFO | --- Analysis for de-budget took 179.87041997909546s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 0.00011491775512695312s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0007946491241455078s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 38.43404293060303s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02126479148864746s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.315376281738281e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 9.298324584960938e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 170.00618815422058s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.982948303222656e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0007841587066650391s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 25.395697593688965s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.023224830627441406s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0010848045349121094s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 6.67572021484375e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.4066696166992188e-05s
INFO | --- Analysis for debian-package-tracking-system took 268.475563287735s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 8.463859558105469e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 59.880086183547974s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.02157878875732422s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.410743713378906e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.3113021850585938e-05s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 61.44008469581604s
Availability | SPARQL endpoint availability check for Demografie took 8.726119995117188e-05s
Availability | VoID file availability check for Demografie took 0.001373291015625s
Completeness | Calculation of interlinking completeness for Demografie took 60.30138373374939s
Reputation | Calculation of the PageRank for Demografie took 0.02263665199279785s
Interlinking | Calculation of Degree of Connection for Demografie took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.9577484130859375e-05s
Believability | Calculation of trust value for Demografie took 1.1920928955078125e-05s
INFO | --- Analysis for demografie took 241.66055393218994s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 9.012222290039062e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 19.444047689437866s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.026024341583251953s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0011332035064697266s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 0.0001087188720703125s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.3113021850585938e-05s
INFO | --- Analysis for desaparecidos took 459.2363066673279s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 9.441375732421875e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.3389310836791992s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.022012710571289062s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010085105895996094s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.1920928955078125e-05s
INFO | --- Analysis for deustoentrepreneurship took 14.163491487503052s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 8.940696716308594e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.8131301403045654s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.4607713222503662s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.021632909774780273s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0009946823120117188s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00013899803161621094s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 9.5367431640625e-06s
INFO | --- Analysis for deustotech took 7.538198232650757s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 4.115065574645996s
Availability | VoID file availability check for Deutsche Biographie took 0.0007927417755126953s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.33744025230407715s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0008764266967773438s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.1961669921875e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.239776611328125e-05s
INFO | --- Analysis for deutsche-biographie took 6.701534271240234s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.797645568847656e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.5938916206359863s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.021523714065551758s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.817413330078125e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.1444091796875e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 7.527486801147461s
Availability | SPARQL endpoint availability check for dev8d took 8.988380432128906e-05s
Availability | VoID file availability check for dev8d took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for dev8d took 0.33592796325683594s
Reputation | Calculation of the PageRank for dev8d took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.2479248046875e-05s
Believability | Calculation of trust value for dev8d took 1.239776611328125e-05s
INFO | --- Analysis for dev8d took 3.368013858795166s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.09872579574585s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.4717271327972412s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.02079153060913086s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 6.508827209472656e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.0728836059570312e-05s
INFO | --- Analysis for dewey_decimal_classification took 72.35246086120605s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 9.036064147949219e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0003886222839355469s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.6064159870147705s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.026212692260742188s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0012438297271728516s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.933906555175781e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.2159347534179688e-05s
INFO | --- Analysis for DHSVM took 17.948965787887573s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 9.012222290039062e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.334247350692749s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.021077632904052734s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 2.86102294921875e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 1.2874603271484375e-05s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.5345377922058105s
Availability | SPARQL endpoint availability check for Diavgeia took 0.8166306018829346s
Availability | VoID file availability check for Diavgeia took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.33818721771240234s
Reputation | Calculation of the PageRank for Diavgeia took 0.021776437759399414s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.606910705566406e-05s
Believability | Calculation of trust value for Diavgeia took 1.049041748046875e-05s
INFO | --- Analysis for diavgeia took 6.005468845367432s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 9.083747863769531e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.5557026863098145s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.36429762840270996s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02144336700439453s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0001163482666015625s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.2874603271484375e-05s
INFO | --- Analysis for didactalia took 9.236738681793213s
Availability | SPARQL endpoint availability check for diigo.feed took 9.298324584960938e-05s
Availability | VoID file availability check for diigo.feed took 0.0009131431579589844s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.33934783935546875s
Reputation | Calculation of the PageRank for diigo.feed took 0.022753000259399414s
Interlinking | Calculation of Degree of Connection for diigo.feed took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.9802322387695312e-05s
Believability | Calculation of trust value for diigo.feed took 1.1920928955078125e-05s
INFO | --- Analysis for diigo-feed took 32.25085210800171s
Availability | SPARQL endpoint availability check for DisGeNET took 2.168581247329712s
Availability | VoID file availability check for DisGeNET took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.3400540351867676s
Reputation | Calculation of the PageRank for DisGeNET took 0.02097153663635254s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015997886657714844s
Believability | Calculation of trust value for DisGeNET took 4.100799560546875e-05s
INFO | --- Analysis for disgenet took 9.897330045700073s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 8.7738037109375e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.7590765953063965s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.022461891174316406s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 1.3113021850585938e-05s
INFO | --- Analysis for disk took 3.5848007202148438s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 8.916854858398438e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.6027939319610596s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.023265600204467773s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0011138916015625s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.814697265625e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 1.239776611328125e-05s
INFO | --- Analysis for distritos-zaragoza took 4.224214553833008s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 9.179115295410156e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 1.6075897216796875s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.021818161010742188s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0009980201721191406s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.743171691894531e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.239776611328125e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 19.24358057975769s
Availability | SPARQL endpoint availability check for DM2E took 9.274482727050781e-05s
Availability | VoID file availability check for DM2E took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for DM2E took 0.3345823287963867s
Reputation | Calculation of the PageRank for DM2E took 0.021311044692993164s
Interlinking | Calculation of Degree of Connection for DM2E took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DM2E took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00012183189392089844s
Believability | Calculation of trust value for DM2E took 1.1920928955078125e-05s
INFO | --- Analysis for dm2e took 3.7312111854553223s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 9.131431579589844e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.34043383598327637s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.022470474243164062s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.0994415283203125e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 1.1682510375976562e-05s
INFO | --- Analysis for dmoz_rdf_dump took 3.987734794616699s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 4.887580871582031e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.7346746921539307s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020861387252807617s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015854835510253906s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.1444091796875e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 13.743274688720703s
Availability | SPARQL endpoint availability check for DOAP Store took 9.083747863769531e-05s
Availability | VoID file availability check for DOAP Store took 0.0008196830749511719s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.3402864933013916s
Reputation | Calculation of the PageRank for DOAP Store took 0.021009445190429688s
Interlinking | Calculation of Degree of Connection for DOAP Store took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.4332275390625e-05s
Believability | Calculation of trust value for DOAP Store took 1.239776611328125e-05s
INFO | --- Analysis for doap_store took 23.065086364746094s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 6.103515625e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.43187522888183594s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.318092346191406e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 1.049041748046875e-05s
INFO | --- Analysis for doi took 7.879630088806152s
Availability | SPARQL endpoint availability check for Driggu Florentino took 9.1552734375e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.355358362197876s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.021489620208740234s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.0517578125e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.3113021850585938e-05s
INFO | --- Analysis for Driggu took 3.403602361679077s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 2.0050437450408936s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.3379628658294678s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.02286553382873535s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.743171691894531e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.3113021850585938e-05s
INFO | --- Analysis for drug-data-hifm took 18.609591245651245s
Availability | SPARQL endpoint availability check for dspace took 0.00013446807861328125s
Availability | VoID file availability check for dspace took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for dspace took 0.6462085247039795s
Reputation | Calculation of the PageRank for dspace took 0.02136707305908203s
Interlinking | Calculation of Degree of Connection for dspace took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for dspace took 3.0517578125e-05s
Believability | Calculation of trust value for dspace took 1.0728836059570312e-05s
INFO | --- Analysis for dspace took 4.3838112354278564s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 0.8948202133178711s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.4473552703857422s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.02107977867126465s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.0517578125e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 1.239776611328125e-05s
INFO | --- Analysis for duraark-linked-building-data took 6.118333578109741s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.07521200180054s
Availability | VoID file availability check for MetaLex Document Server took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.3905510902404785s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.021224021911621094s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.814697265625e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.2874603271484375e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 414.1386253833771s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.0871107578277588s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.33479928970336914s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.023256301879882812s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.001100778579711914s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.5299530029296875e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.2874603271484375e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 12.628462076187134s
Availability | SPARQL endpoint availability check for DWS-Group took 9.250640869140625e-05s
Availability | VoID file availability check for DWS-Group took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.6737933158874512s
Reputation | Calculation of the PageRank for DWS-Group took 0.021207094192504883s
Interlinking | Calculation of Degree of Connection for DWS-Group took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010728836059570312s
Believability | Calculation of trust value for DWS-Group took 1.2874603271484375e-05s
INFO | --- Analysis for dws-group took 3.395962715148926s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 9.942054748535156e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0008225440979003906s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.4479684829711914s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.021453380584716797s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.956390380859375e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.0728836059570312e-05s
INFO | --- Analysis for E1 took 4.143041610717773s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 30.13497495651245s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0008196830749511719s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.3385913372039795s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00012826919555664062s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-alaska took 73.55919408798218s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 30.117610216140747s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.3702857494354248s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.023162126541137695s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0010623931884765625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 8.320808410644531e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-cau took 73.42507815361023s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 30.122101068496704s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.4661407470703125s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020888566970825195s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.651878356933594e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 74.7602310180664s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 30.212939500808716s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.3402366638183594s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020914793014526367s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 0.00011110305786132812s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-cdrewu took 72.79000234603882s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 30.122477054595947s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.29793381690979004s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001418590545654297s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-dartmouth took 72.68203663825989s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 30.036924600601196s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.31519055366516113s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.021237611770629883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0008742809295654297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 0.00010371208190917969s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-famu took 74.96964454650879s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.03174090385437012s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.45166563987731934s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00014281272888183594s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-harvard took 5.415583848953247s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 30.144838094711304s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0009047985076904297s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 3.2652575969696045s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.024066686630249023s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0011837482452392578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00017786026000976562s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-hawaii took 77.00759220123291s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 30.119688272476196s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 2.949519157409668s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.021564245223999023s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0010333061218261719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 8.225440979003906e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-howard took 75.85783386230469s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 30.116344690322876s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0007970333099365234s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 1.0378520488739014s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.508827209472656e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 83.55753827095032s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 30.05393362045288s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 2.4452152252197266s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.023070335388183594s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0013072490692138672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00016427040100097656s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-jsu took 79.24223613739014s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 30.136764764785767s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0007979869842529297s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 1.031874656677246s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 5.841255187988281e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-meharry took 84.92099094390869s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 30.11652708053589s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 3.337618350982666s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020943641662597656s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0012009143829345703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.0001342296600341797s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-montana took 84.47992062568665s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 30.039994478225708s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 2.1581437587738037s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0008993148803710938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 0.00013399124145507812s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-msm took 114.82114696502686s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 30.118943214416504s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 108.07853746414185s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02092576026916504s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00013899803161621094s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-ohsu took 195.38690948486328s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 30.2332603931427s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.4216442108154297s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020959854125976562s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-psm took 181.3140947818756s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 30.03544330596924s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0008571147918701172s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 120.23315191268921s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.021453857421875s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 7.867813110351562e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.8835067749023438e-05s
INFO | --- Analysis for eagle-i-tsu took 645.4530200958252s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 30.059189319610596s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 6.946613311767578s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.021904706954956055s
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.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 7.915496826171875e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-tuskegee took 123.95313429832458s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 30.2535400390625s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 60.038435220718384s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.021613597869873047s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0010454654693603516s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.0001404285430908203s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-uccaribe took 240.14188289642334s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 30.300474643707275s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 60.151655435562134s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.021326541900634766s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00015115737915039062s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-upr took 649.4517440795898s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 30.335938930511475s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.000797271728515625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.3858153820037842s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.021470069885253906s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 7.43865966796875e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-utep took 221.09072732925415s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 30.13041043281555s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0010268688201904297s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.3424375057220459s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.023091554641723633s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0009515285491943359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 0.000102996826171875s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-utsa took 72.9973533153534s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.1548631191253662s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.4889805316925049s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.021286964416503906s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.465217590332031e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 4.45047926902771s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 30.045671224594116s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 1.859292984008789s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020995616912841797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.796287536621094e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-xula took 76.74697923660278s
Availability | SPARQL endpoint availability check for Emergency situation took 0.767249584197998s
Availability | VoID file availability check for Emergency situation took 0.0003807544708251953s
Completeness | Calculation of interlinking completeness for Emergency situation took 1.107515573501587s
Reputation | Calculation of the PageRank for Emergency situation took 0.021027088165283203s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.744529724121094e-05s
Believability | Calculation of trust value for Emergency situation took 1.1920928955078125e-05s
INFO | --- Analysis for Earthquake took 5.563170433044434s
Availability | SPARQL endpoint availability check for ESO took 0.5967469215393066s
Availability | VoID file availability check for ESO took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for ESO took 1.5511908531188965s
Reputation | Calculation of the PageRank for ESO took 0.020862579345703125s
Interlinking | Calculation of Degree of Connection for ESO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for ESO took 9.131431579589844e-05s
Believability | Calculation of trust value for ESO took 1.1444091796875e-05s
INFO | --- Analysis for Earthquake_case took 5.813452243804932s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.12203097343444824s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0004057884216308594s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.33032751083374023s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.021377086639404297s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010728836059570312s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for ecb-linked-data took 2.0905921459198s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 2.786924362182617s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.46704697608947754s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.029273986816406e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 1.049041748046875e-05s
INFO | --- Analysis for ecb-statistics-linked-data took 13.742948532104492s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.6389589309692383s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 1.03806471824646s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.021050691604614258s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.914138793945312e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 8.140073537826538s
Availability | SPARQL endpoint availability check for ECLAP took 20.196088790893555s
Availability | VoID file availability check for ECLAP took 0.0004096031188964844s
Completeness | Calculation of interlinking completeness for ECLAP took 0.7627532482147217s
Reputation | Calculation of the PageRank for ECLAP took 0.021385669708251953s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.220008850097656e-05s
Believability | Calculation of trust value for ECLAP took 8.58306884765625e-06s
INFO | --- Analysis for eclap took 33.332961082458496s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.482269287109375e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.48540592193603516s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.033358097076416016s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0014562606811523438s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 9.298324584960938e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.239776611328125e-05s
INFO | --- Analysis for ecs took 3.1139450073242188s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 9.465217590332031e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 3.120981216430664s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.028515100479125977s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0015974044799804688s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 5.0067901611328125e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 1.1682510375976562e-05s
INFO | --- Analysis for edificios-historicos-zaragoza took 10.236469745635986s
Availability | SPARQL endpoint availability check for Edublogs took 8.821487426757812e-05s
Availability | VoID file availability check for Edublogs took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for Edublogs took 0.4868042469024658s
Reputation | Calculation of the PageRank for Edublogs took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for Edublogs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Edublogs took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010180473327636719s
Believability | Calculation of trust value for Edublogs took 1.1682510375976562e-05s
INFO | --- Analysis for edublogs took 4.018960237503052s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.8565835952758789s
Availability | VoID file availability check for education.data.gov.uk took 0.407578706741333s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 1.398723840713501s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.023099899291992188s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0011801719665527344s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 0.00013971328735351562s
Believability | Calculation of trust value for education.data.gov.uk took 4.5299530029296875e-06s
INFO | --- Analysis for education-data-gov-uk took 8.257813215255737s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 0.06177115440368652s
Availability | VoID file availability check for OpenUpLabs Education took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.34683704376220703s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.021152734756469727s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0009102821350097656s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.528594970703125e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 1.3113021850585938e-05s
INFO | --- Analysis for education-openuplabs took 11.351195573806763s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.37423491477966s
Availability | VoID file availability check for Educational programs - SISVU took 0.001422882080078125s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.5214557647705078s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02208733558654785s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0008957386016845703s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 6.747245788574219e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.1920928955078125e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1184.1698007583618s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.2371437549591064s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 180.0041618347168s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02141284942626953s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 5.412101745605469e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 1.2874603271484375e-05s
INFO | --- Analysis for eea took 549.3269391059875s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5690009593963623s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.6688013076782227s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.3442566394805908s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02161884307861328s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for EEA Reporting Obligations Database took 8.548450231552124s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 9.298324584960938e-06s
INFO | --- Analysis for eea-rod took 29.943069219589233s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.25283169746398926s
Availability | VoID file availability check for EEA Vocabularies took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 1.2061879634857178s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.022766590118408203s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0011000633239746094s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 0.0001087188720703125s
Believability | Calculation of trust value for EEA Vocabularies took 1.4543533325195312e-05s
INFO | --- Analysis for eea-vocabularies took 6.117140293121338s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 32.64931297302246s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.3555939197540283s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.021446704864501953s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.5762786865234375e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for ege-university-linked-open-data took 45.90060329437256s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.9954640865325928s
Availability | VoID file availability check for E-Government Ontology took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.3522958755493164s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.02214956283569336s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0010955333709716797s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.838539123535156e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for EGovOntology took 4.545626401901245s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5255937576293945s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006442070007324219s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.519792079925537s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1351325511932373s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6852266788482666s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8890345096588135s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.384480714797974s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 3.764519691467285s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.49765706062316895s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22958803176879883s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23037362098693848s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.42479515075683594s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.189388275146484s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23703742027282715s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3389909267425537s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5075099468231201s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25298619270324707s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5632617473602295s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2333066463470459s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.130878686904907s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 8.940696716308594e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2804570198059082s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.21898245811462402s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.35420823097229004s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22655868530273438s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27425551414489746s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2297077178955078s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4578680992126465s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.998558044433594s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.21899700164794922s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26785707473754883s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2718949317932129s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0985047817230225s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030344724655151367s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.028455495834350586s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22245025634765625s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.220086574554443s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.42528676986694336s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.2045555114746094s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1481003761291504s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.238794326782227s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.037790536880493164s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40664005279541016s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3871605396270752s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3195.853049993515s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 171.93654322624207s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.022007465362548828s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 7.62939453125e-06s
INFO | --- Analysis for ei2a took 3575.406331539154s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 0.35015034675598145s
Availability | VoID file availability check for EIONET RDF Data took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 12.032819032669067s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.02238631248474121s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.0001068115234375s
Believability | Calculation of trust value for EIONET RDF Data took 9.059906005859375e-06s
INFO | --- Analysis for eionet-rdf took 15.624175786972046s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 8.988380432128906e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.33191657066345215s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.021413087844848633s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 2.956390380859375e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.0728836059570312e-05s
INFO | --- Analysis for ElgooG_ took 2.060734987258911s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 0.2090775966644287s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0005517005920410156s
Extra | Recovery of all triples for ELTE Digital Institutional Repository (EDIT) took 16.16499662399292s
Performance | Total latancy measurement for ELTE Digital Institutional Repository (EDIT) took 0.44419217109680176s
Amount of data | Number of triples check for ELTE Digital Institutional Repository (EDIT) took 4.23527979850769s
Interoperability | New terms check for ELTE Digital Institutional Repository (EDIT) took 1.3085107803344727s
Versatility | Languages check for ELTE Digital Institutional Repository (EDIT) took 18.992549896240234s
Interpretability | Number of blank nodes check for ELTE Digital Institutional Repository (EDIT) took 2.4265129566192627s
Security | Check HTTPS for ELTE Digital Institutional Repository (EDIT) took 0.11022472381591797s
Interpretability | RDF structures check for ELTE Digital Institutional Repository (EDIT) took 0.14977049827575684s
Versatility | Serialization formats check for ELTE Digital Institutional Repository (EDIT) took 0.13223719596862793s
Availability | RDF dump link check for ELTE Digital Institutional Repository (EDIT) took 0.0665440559387207s
License | MR license check for ELTE Digital Institutional Repository (EDIT) took 0.1384580135345459s
License | HR license check for ELTE Digital Institutional Repository (EDIT) took 0.0708920955657959s
Amount of data | Number of property check for ELTE Digital Institutional Repository (EDIT) took 0.11540985107421875s
Understandability | Number of label check for ELTE Digital Institutional Repository (EDIT) took 1.1671130657196045s
Understandability | URI regex check for ELTE Digital Institutional Repository (EDIT) took 0.15143871307373047s
Understandability | Vocabs check for ELTE Digital Institutional Repository (EDIT) took 0.0616455078125s
Verifiability | Authors check for ELTE Digital Institutional Repository (EDIT) took 3.039435863494873s
Verifiability | Publishers check for ELTE Digital Institutional Repository (EDIT) took 0.4658203125s
Performance | Throughput check for ELTE Digital Institutional Repository (EDIT) took 10.244946718215942s
Amount of data | Check the number of entities for ELTE Digital Institutional Repository (EDIT) took 8.749961853027344e-05s
Verifiability | Contribs. check for ELTE Digital Institutional Repository (EDIT) took 0.0765676498413086s
Interlinking | sameAs chians check for ELTE Digital Institutional Repository (EDIT) took 0.06964468955993652s
Interlinking | skos check for ELTE Digital Institutional Repository (EDIT) took 0.07976078987121582s
Interlinking | skos check for ELTE Digital Institutional Repository (EDIT) took 0.0628962516784668s
Timeliness | dataset update frequency check for ELTE Digital Institutional Repository (EDIT) took 0.07717633247375488s
Currency | Creation date check for ELTE Digital Institutional Repository (EDIT) took 0.40631651878356934s
Currency | Modification date check for ELTE Digital Institutional Repository (EDIT) took 0.17026281356811523s
Rep.Conc. | URIs length for ELTE Digital Institutional Repository (EDIT) took 82.61198210716248s
Interoperability | New vocabularies check for ELTE Digital Institutional Repository (EDIT) took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for ELTE Digital Institutional Repository (EDIT) took 0.1254591941833496s
Accuracy | Check Functional Property for ELTE Digital Institutional Repository (EDIT) took 0.10148167610168457s
Accuracy | Check Inverse Functional Property for ELTE Digital Institutional Repository (EDIT) took 0.06206941604614258s
Accuracy | Check Empty annotation labels for ELTE Digital Institutional Repository (EDIT) took 1.9401524066925049s
Accuracy | Check White space in annotation for ELTE Digital Institutional Repository (EDIT) took 0.3896312713623047s
Accuracy | Check Datatype consistency for ELTE Digital Institutional Repository (EDIT) took 4.867015361785889s
Consistency | Disjoint class check for ELTE Digital Institutional Repository (EDIT) took 0.1651628017425537s
Consistency | Check Misplaced properties for ELTE Digital Institutional Repository (EDIT) took 4.97668981552124s
Consistency | Check Ontology hijacking for ELTE Digital Institutional Repository (EDIT) took 1.2439274787902832s
Consistency | Check Invalid usage of undefined classes for ELTE Digital Institutional Repository (EDIT) took 1.1786863803863525s
Consistency | Check Invalid usage of undefined properties for ELTE Digital Institutional Repository (EDIT) took 6.068783283233643s
Conciseness | Check Extensional conciseness for ELTE Digital Institutional Repository (EDIT) took 3.0904088020324707s
Security | Sign check for ELTE Digital Institutional Repository (EDIT) took 0.09554648399353027s
Availability | Check URIs Dereferenciability for ELTE Digital Institutional Repository (EDIT) took 9.101470232009888s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.4039173126220703s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.021010160446166992s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for ELTE Digital Institutional Repository (EDIT) took 2.1457672119140625e-06s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 1.2159347534179688e-05s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 438.8180515766144s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.226576328277588s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 1.2877087593078613s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.021881580352783203s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 9.012222290039062e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.2874603271484375e-05s
INFO | --- Analysis for elviajero took 23.113211393356323s
Availability | SPARQL endpoint availability check for EMN took 0.00010013580322265625s
Availability | VoID file availability check for EMN took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for EMN took 0.46022915840148926s
Reputation | Calculation of the PageRank for EMN took 0.021315813064575195s
Interlinking | Calculation of Degree of Connection for EMN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for EMN took 4.029273986816406e-05s
Believability | Calculation of trust value for EMN took 1.1920928955078125e-05s
INFO | --- Analysis for emn took 3.2209854125976562s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 0.00010728836059570312s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.7365286350250244s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.046823740005493164s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0022287368774414062s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 0.00020432472229003906s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for enakting-co2emission took 3.7619431018829346s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 8.535385131835938e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.4068477153778076s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.031571388244628906s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0013251304626464844s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 5.459785461425781e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 9.298324584960938e-06s
INFO | --- Analysis for enakting-crime took 2.097562074661255s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 8.96453857421875e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.33913183212280273s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.022433996200561523s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0011234283447265625s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 5.173683166503906e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for enakting-energy took 3.999218463897705s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 9.250640869140625e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.426715612411499s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.033174991607666016s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0014181137084960938s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 0.0001838207244873047s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-mortality took 4.168744087219238s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 8.988380432128906e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.3156142234802246s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02356266975402832s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.600120544433594e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for enakting-nhs took 2.7966036796569824s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 0.00013899803161621094s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.9698295593261719s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.364418029785156e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 8.58306884765625e-06s
INFO | --- Analysis for enakting-population took 4.111703634262085s
Availability | SPARQL endpoint availability check for Enel Shops took 0.00016689300537109375s
Availability | VoID file availability check for Enel Shops took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.8665273189544678s
Reputation | Calculation of the PageRank for Enel Shops took 0.022460222244262695s
Interlinking | Calculation of Degree of Connection for Enel Shops took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.0040740966796875e-05s
Believability | Calculation of trust value for Enel Shops took 1.1205673217773438e-05s
INFO | --- Analysis for enel-shops took 3.5968234539031982s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 1.1745855808258057s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.2916243076324463s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.123283386230469e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 1.1444091796875e-05s
INFO | --- Analysis for energy-efficiency took 7.1470537185668945s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 0.736386775970459s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0007908344268798828s
Extra | Recovery of all triples for English Heritage Archaeological Sciences Thesaurus took 0.9665000438690186s
Performance | Total latancy measurement for English Heritage Archaeological Sciences Thesaurus took 2.672210693359375s
Amount of data | Number of triples check for English Heritage Archaeological Sciences Thesaurus took 1.3431148529052734s
Versatility | Languages check for English Heritage Archaeological Sciences Thesaurus took 0.3372948169708252s
Interpretability | Number of blank nodes check for English Heritage Archaeological Sciences Thesaurus took 0.9104337692260742s
Security | Check HTTPS for English Heritage Archaeological Sciences Thesaurus took 0.4591987133026123s
Interpretability | RDF structures check for English Heritage Archaeological Sciences Thesaurus took 0.39299893379211426s
Versatility | Serialization formats check for English Heritage Archaeological Sciences Thesaurus took 0.8654913902282715s
Availability | RDF dump link check for English Heritage Archaeological Sciences Thesaurus took 0.5578110218048096s
License | MR license check for English Heritage Archaeological Sciences Thesaurus took 0.8533899784088135s
License | HR license check for English Heritage Archaeological Sciences Thesaurus took 0.909966230392456s
Amount of data | Number of property check for English Heritage Archaeological Sciences Thesaurus took 0.7266700267791748s
Understandability | Number of label check for English Heritage Archaeological Sciences Thesaurus took 1.0874946117401123s
Understandability | URI regex check for English Heritage Archaeological Sciences Thesaurus took 1.1800947189331055s
Understandability | Vocabs check for English Heritage Archaeological Sciences Thesaurus took 0.537391185760498s
Verifiability | Authors check for English Heritage Archaeological Sciences Thesaurus took 4.243350505828857s
Verifiability | Publishers check for English Heritage Archaeological Sciences Thesaurus took 0.8248744010925293s
Performance | Throughput check for English Heritage Archaeological Sciences Thesaurus took 14.296281576156616s
Amount of data | Check the number of entities for English Heritage Archaeological Sciences Thesaurus took 9.059906005859375e-05s
Verifiability | Contribs. check for English Heritage Archaeological Sciences Thesaurus took 0.35083723068237305s
Interlinking | sameAs chians check for English Heritage Archaeological Sciences Thesaurus took 0.6351268291473389s
Interlinking | skos check for English Heritage Archaeological Sciences Thesaurus took 0.4909195899963379s
Interlinking | skos check for English Heritage Archaeological Sciences Thesaurus took 0.6749551296234131s
Timeliness | dataset update frequency check for English Heritage Archaeological Sciences Thesaurus took 0.6605923175811768s
Currency | Creation date check for English Heritage Archaeological Sciences Thesaurus took 1.0176069736480713s
Currency | Modification date check for English Heritage Archaeological Sciences Thesaurus took 0.7977275848388672s
Rep.Conc. | URIs length for English Heritage Archaeological Sciences Thesaurus took 0.8652393817901611s
Interoperability | New vocabularies check for English Heritage Archaeological Sciences Thesaurus took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Archaeological Sciences Thesaurus took 0.7801930904388428s
Accuracy | Check Functional Property for English Heritage Archaeological Sciences Thesaurus took 0.6205785274505615s
Accuracy | Check Inverse Functional Property for English Heritage Archaeological Sciences Thesaurus took 0.5572149753570557s
Consistency | Disjoint class check for English Heritage Archaeological Sciences Thesaurus took 0.5619165897369385s
Consistency | Check Ontology hijacking for English Heritage Archaeological Sciences Thesaurus took 0.4884815216064453s
Consistency | Check Invalid usage of undefined properties for English Heritage Archaeological Sciences Thesaurus took 1.8394274711608887s
Conciseness | Check Extensional conciseness for English Heritage Archaeological Sciences Thesaurus took 0.00018739700317382812s
Security | Sign check for English Heritage Archaeological Sciences Thesaurus took 0.5255434513092041s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.45354509353637695s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.022188186645507812s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.218650817871094e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Archaeological Sciences Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 97.76127004623413s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 1.6859080791473389s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.0007169246673583984s
Extra | Recovery of all triples for English Heritage Building Materials Thesaurus took 0.5291602611541748s
Performance | Total latancy measurement for English Heritage Building Materials Thesaurus took 2.7102761268615723s
Amount of data | Number of triples check for English Heritage Building Materials Thesaurus took 0.6690945625305176s
Versatility | Languages check for English Heritage Building Materials Thesaurus took 0.3069725036621094s
Interpretability | Number of blank nodes check for English Heritage Building Materials Thesaurus took 0.6151177883148193s
Security | Check HTTPS for English Heritage Building Materials Thesaurus took 0.42981886863708496s
Interpretability | RDF structures check for English Heritage Building Materials Thesaurus took 0.4066312313079834s
Versatility | Serialization formats check for English Heritage Building Materials Thesaurus took 0.7157132625579834s
Availability | RDF dump link check for English Heritage Building Materials Thesaurus took 0.40522289276123047s
License | MR license check for English Heritage Building Materials Thesaurus took 0.671238899230957s
License | HR license check for English Heritage Building Materials Thesaurus took 0.7384088039398193s
Amount of data | Number of property check for English Heritage Building Materials Thesaurus took 0.7414681911468506s
Understandability | Number of label check for English Heritage Building Materials Thesaurus took 0.9476711750030518s
Understandability | URI regex check for English Heritage Building Materials Thesaurus took 1.0920085906982422s
Understandability | Vocabs check for English Heritage Building Materials Thesaurus took 4.105561256408691s
Verifiability | Authors check for English Heritage Building Materials Thesaurus took 0.7648684978485107s
Verifiability | Publishers check for English Heritage Building Materials Thesaurus took 0.638761043548584s
Performance | Throughput check for English Heritage Building Materials Thesaurus took 12.657252550125122s
Amount of data | Check the number of entities for English Heritage Building Materials Thesaurus took 7.05718994140625e-05s
Verifiability | Contribs. check for English Heritage Building Materials Thesaurus took 0.421156644821167s
Interlinking | sameAs chians check for English Heritage Building Materials Thesaurus took 0.5037393569946289s
Interlinking | skos check for English Heritage Building Materials Thesaurus took 0.47644615173339844s
Interlinking | skos check for English Heritage Building Materials Thesaurus took 1.0066280364990234s
Timeliness | dataset update frequency check for English Heritage Building Materials Thesaurus took 0.5446345806121826s
Currency | Creation date check for English Heritage Building Materials Thesaurus took 1.3165826797485352s
Currency | Modification date check for English Heritage Building Materials Thesaurus took 1.1563241481781006s
Rep.Conc. | URIs length for English Heritage Building Materials Thesaurus took 1.075833797454834s
Interoperability | New vocabularies check for English Heritage Building Materials Thesaurus took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Building Materials Thesaurus took 0.5797920227050781s
Accuracy | Check Functional Property for English Heritage Building Materials Thesaurus took 0.8146474361419678s
Accuracy | Check Inverse Functional Property for English Heritage Building Materials Thesaurus took 0.357865571975708s
Consistency | Disjoint class check for English Heritage Building Materials Thesaurus took 0.6998822689056396s
Consistency | Check Ontology hijacking for English Heritage Building Materials Thesaurus took 0.648320198059082s
Consistency | Check Invalid usage of undefined properties for English Heritage Building Materials Thesaurus took 4.520441293716431s
Conciseness | Check Extensional conciseness for English Heritage Building Materials Thesaurus took 0.00016951560974121094s
Security | Sign check for English Heritage Building Materials Thesaurus took 0.5523595809936523s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 3.1190764904022217s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.021961212158203125s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.0040740966796875e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Building Materials Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 104.23912715911865s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 0.44126129150390625s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0008671283721923828s
Extra | Recovery of all triples for English Heritage Components Thesaurus took 0.3817121982574463s
Performance | Total latancy measurement for English Heritage Components Thesaurus took 2.8981575965881348s
Amount of data | Number of triples check for English Heritage Components Thesaurus took 0.7419557571411133s
Versatility | Languages check for English Heritage Components Thesaurus took 0.4156801700592041s
Interpretability | Number of blank nodes check for English Heritage Components Thesaurus took 0.7121152877807617s
Security | Check HTTPS for English Heritage Components Thesaurus took 0.31981658935546875s
Interpretability | RDF structures check for English Heritage Components Thesaurus took 0.36837220191955566s
Versatility | Serialization formats check for English Heritage Components Thesaurus took 0.5776495933532715s
Availability | RDF dump link check for English Heritage Components Thesaurus took 0.5469567775726318s
License | MR license check for English Heritage Components Thesaurus took 0.7768054008483887s
License | HR license check for English Heritage Components Thesaurus took 0.7962245941162109s
Amount of data | Number of property check for English Heritage Components Thesaurus took 1.3977172374725342s
Understandability | Number of label check for English Heritage Components Thesaurus took 0.6355986595153809s
Understandability | URI regex check for English Heritage Components Thesaurus took 4.683466672897339s
Understandability | Vocabs check for English Heritage Components Thesaurus took 0.8070323467254639s
Verifiability | Authors check for English Heritage Components Thesaurus took 0.39722108840942383s
Verifiability | Publishers check for English Heritage Components Thesaurus took 0.94207763671875s
Performance | Throughput check for English Heritage Components Thesaurus took 18.59685254096985s
Amount of data | Check the number of entities for English Heritage Components Thesaurus took 8.845329284667969e-05s
Verifiability | Contribs. check for English Heritage Components Thesaurus took 0.48819565773010254s
Interlinking | sameAs chians check for English Heritage Components Thesaurus took 0.5869853496551514s
Interlinking | skos check for English Heritage Components Thesaurus took 0.48885393142700195s
Interlinking | skos check for English Heritage Components Thesaurus took 0.45667338371276855s
Timeliness | dataset update frequency check for English Heritage Components Thesaurus took 0.47922229766845703s
Currency | Creation date check for English Heritage Components Thesaurus took 1.2136857509613037s
Currency | Modification date check for English Heritage Components Thesaurus took 0.8008646965026855s
Rep.Conc. | URIs length for English Heritage Components Thesaurus took 1.0026519298553467s
Interoperability | New vocabularies check for English Heritage Components Thesaurus took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Components Thesaurus took 2.0828022956848145s
Accuracy | Check Functional Property for English Heritage Components Thesaurus took 0.5107729434967041s
Accuracy | Check Inverse Functional Property for English Heritage Components Thesaurus took 0.4742283821105957s
Consistency | Disjoint class check for English Heritage Components Thesaurus took 0.6958105564117432s
Consistency | Check Ontology hijacking for English Heritage Components Thesaurus took 0.6423306465148926s
Consistency | Check Invalid usage of undefined properties for English Heritage Components Thesaurus took 6.015381813049316s
Conciseness | Check Extensional conciseness for English Heritage Components Thesaurus took 0.0001628398895263672s
Security | Sign check for English Heritage Components Thesaurus took 0.4487888813018799s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.3621327877044678s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.023339033126831055s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Components Thesaurus took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for english-heritage-components-thesaurus took 108.7889130115509s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 3.3298096656799316s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00037169456481933594s
Extra | Recovery of all triples for English Heritage Event Types Thesaurus took 0.513063907623291s
Performance | Total latancy measurement for English Heritage Event Types Thesaurus took 3.4502196311950684s
Amount of data | Number of triples check for English Heritage Event Types Thesaurus took 0.48412013053894043s
Versatility | Languages check for English Heritage Event Types Thesaurus took 0.37070274353027344s
Interpretability | Number of blank nodes check for English Heritage Event Types Thesaurus took 0.8033742904663086s
Security | Check HTTPS for English Heritage Event Types Thesaurus took 0.36081790924072266s
Interpretability | RDF structures check for English Heritage Event Types Thesaurus took 0.29570913314819336s
Versatility | Serialization formats check for English Heritage Event Types Thesaurus took 0.6748640537261963s
Availability | RDF dump link check for English Heritage Event Types Thesaurus took 0.6910979747772217s
License | MR license check for English Heritage Event Types Thesaurus took 1.1683428287506104s
License | HR license check for English Heritage Event Types Thesaurus took 0.5214433670043945s
Amount of data | Number of property check for English Heritage Event Types Thesaurus took 0.5963015556335449s
Understandability | Number of label check for English Heritage Event Types Thesaurus took 1.9362750053405762s
Understandability | URI regex check for English Heritage Event Types Thesaurus took 1.2624351978302002s
Understandability | Vocabs check for English Heritage Event Types Thesaurus took 0.4990811347961426s
Verifiability | Authors check for English Heritage Event Types Thesaurus took 0.8089096546173096s
Verifiability | Publishers check for English Heritage Event Types Thesaurus took 0.6754307746887207s
Performance | Throughput check for English Heritage Event Types Thesaurus took 19.518729209899902s
Amount of data | Check the number of entities for English Heritage Event Types Thesaurus took 8.249282836914062e-05s
Verifiability | Contribs. check for English Heritage Event Types Thesaurus took 0.9081020355224609s
Interlinking | sameAs chians check for English Heritage Event Types Thesaurus took 0.9509973526000977s
Interlinking | skos check for English Heritage Event Types Thesaurus took 0.9213716983795166s
Interlinking | skos check for English Heritage Event Types Thesaurus took 1.3615672588348389s
Timeliness | dataset update frequency check for English Heritage Event Types Thesaurus took 1.3080980777740479s
Currency | Creation date check for English Heritage Event Types Thesaurus took 1.8955881595611572s
Currency | Modification date check for English Heritage Event Types Thesaurus took 3.090339183807373s
Rep.Conc. | URIs length for English Heritage Event Types Thesaurus took 1.317612648010254s
Interoperability | New vocabularies check for English Heritage Event Types Thesaurus took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Event Types Thesaurus took 0.6036758422851562s
Accuracy | Check Functional Property for English Heritage Event Types Thesaurus took 6.93194580078125s
Accuracy | Check Inverse Functional Property for English Heritage Event Types Thesaurus took 0.8726773262023926s
Consistency | Disjoint class check for English Heritage Event Types Thesaurus took 0.6544458866119385s
Consistency | Check Ontology hijacking for English Heritage Event Types Thesaurus took 0.6402065753936768s
Consistency | Check Invalid usage of undefined properties for English Heritage Event Types Thesaurus took 1.8824119567871094s
Conciseness | Check Extensional conciseness for English Heritage Event Types Thesaurus took 0.0001418590545654297s
Security | Sign check for English Heritage Event Types Thesaurus took 0.6385865211486816s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.9170994758605957s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.021054983139038086s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 2.956390380859375e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Event Types Thesaurus took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 112.06946611404419s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 8.463859558105469e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 2.2100727558135986s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.022162914276123047s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.001352548599243164s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 4.553794860839844e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 7.231507778167725s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 0.5883080959320068s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0010476112365722656s
Extra | Recovery of all triples for English Heritage Maritime Craft Thesaurus took 0.8632898330688477s
Performance | Total latancy measurement for English Heritage Maritime Craft Thesaurus took 3.8528823852539062s
Amount of data | Number of triples check for English Heritage Maritime Craft Thesaurus took 0.9042572975158691s
Versatility | Languages check for English Heritage Maritime Craft Thesaurus took 0.6450777053833008s
Interpretability | Number of blank nodes check for English Heritage Maritime Craft Thesaurus took 0.8718776702880859s
Security | Check HTTPS for English Heritage Maritime Craft Thesaurus took 0.5942754745483398s
Interpretability | RDF structures check for English Heritage Maritime Craft Thesaurus took 0.5868422985076904s
Versatility | Serialization formats check for English Heritage Maritime Craft Thesaurus took 0.5962479114532471s
Availability | RDF dump link check for English Heritage Maritime Craft Thesaurus took 0.929154634475708s
License | MR license check for English Heritage Maritime Craft Thesaurus took 2.65381121635437s
License | HR license check for English Heritage Maritime Craft Thesaurus took 1.614628553390503s
Amount of data | Number of property check for English Heritage Maritime Craft Thesaurus took 1.5936505794525146s
Understandability | Number of label check for English Heritage Maritime Craft Thesaurus took 2.057603359222412s
Understandability | URI regex check for English Heritage Maritime Craft Thesaurus took 1.5105252265930176s
Understandability | Vocabs check for English Heritage Maritime Craft Thesaurus took 0.7279536724090576s
Verifiability | Authors check for English Heritage Maritime Craft Thesaurus took 0.8722829818725586s
Verifiability | Publishers check for English Heritage Maritime Craft Thesaurus took 0.5943493843078613s
Performance | Throughput check for English Heritage Maritime Craft Thesaurus took 15.083591938018799s
Amount of data | Check the number of entities for English Heritage Maritime Craft Thesaurus took 8.225440979003906e-05s
Verifiability | Contribs. check for English Heritage Maritime Craft Thesaurus took 0.6530313491821289s
Interlinking | sameAs chians check for English Heritage Maritime Craft Thesaurus took 0.5885517597198486s
Interlinking | skos check for English Heritage Maritime Craft Thesaurus took 0.910832405090332s
Interlinking | skos check for English Heritage Maritime Craft Thesaurus took 0.6342222690582275s
Timeliness | dataset update frequency check for English Heritage Maritime Craft Thesaurus took 0.8900701999664307s
Currency | Creation date check for English Heritage Maritime Craft Thesaurus took 1.6430375576019287s
Currency | Modification date check for English Heritage Maritime Craft Thesaurus took 1.4459848403930664s
Rep.Conc. | URIs length for English Heritage Maritime Craft Thesaurus took 1.1316215991973877s
Interoperability | New vocabularies check for English Heritage Maritime Craft Thesaurus took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Maritime Craft Thesaurus took 0.6309757232666016s
Accuracy | Check Functional Property for English Heritage Maritime Craft Thesaurus took 0.6029126644134521s
Accuracy | Check Inverse Functional Property for English Heritage Maritime Craft Thesaurus took 0.6774697303771973s
Consistency | Disjoint class check for English Heritage Maritime Craft Thesaurus took 0.5558676719665527s
Consistency | Check Ontology hijacking for English Heritage Maritime Craft Thesaurus took 0.865408182144165s
Consistency | Check Invalid usage of undefined properties for English Heritage Maritime Craft Thesaurus took 1.8083295822143555s
Conciseness | Check Extensional conciseness for English Heritage Maritime Craft Thesaurus took 0.0001595020294189453s
Security | Sign check for English Heritage Maritime Craft Thesaurus took 0.8929557800292969s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.622328519821167s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Maritime Craft Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 103.18576002120972s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 0.9036989212036133s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0008432865142822266s
Extra | Recovery of all triples for English Heritage Monument Types Thesaurus took 7.792396068572998s
Performance | Total latancy measurement for English Heritage Monument Types Thesaurus took 3.722747325897217s
Amount of data | Number of triples check for English Heritage Monument Types Thesaurus took 0.7116496562957764s
Versatility | Languages check for English Heritage Monument Types Thesaurus took 0.5815634727478027s
Interpretability | Number of blank nodes check for English Heritage Monument Types Thesaurus took 0.8613455295562744s
Security | Check HTTPS for English Heritage Monument Types Thesaurus took 0.5458471775054932s
Interpretability | RDF structures check for English Heritage Monument Types Thesaurus took 0.5622329711914062s
Versatility | Serialization formats check for English Heritage Monument Types Thesaurus took 0.8487181663513184s
Availability | RDF dump link check for English Heritage Monument Types Thesaurus took 0.843087911605835s
License | MR license check for English Heritage Monument Types Thesaurus took 1.2691686153411865s
License | HR license check for English Heritage Monument Types Thesaurus took 0.9892241954803467s
Amount of data | Number of property check for English Heritage Monument Types Thesaurus took 1.4247629642486572s
Understandability | Number of label check for English Heritage Monument Types Thesaurus took 3.76379656791687s
Understandability | URI regex check for English Heritage Monument Types Thesaurus took 2.315650224685669s
Understandability | Vocabs check for English Heritage Monument Types Thesaurus took 0.5454957485198975s
Verifiability | Authors check for English Heritage Monument Types Thesaurus took 0.8817036151885986s
Verifiability | Publishers check for English Heritage Monument Types Thesaurus took 2.4059269428253174s
Performance | Throughput check for English Heritage Monument Types Thesaurus took 15.625562191009521s
Amount of data | Check the number of entities for English Heritage Monument Types Thesaurus took 3.933906555175781e-05s
Verifiability | Contribs. check for English Heritage Monument Types Thesaurus took 0.5586302280426025s
Interlinking | sameAs chians check for English Heritage Monument Types Thesaurus took 0.905789852142334s
Interlinking | skos check for English Heritage Monument Types Thesaurus took 0.49083662033081055s
Interlinking | skos check for English Heritage Monument Types Thesaurus took 1.0326509475708008s
Timeliness | dataset update frequency check for English Heritage Monument Types Thesaurus took 0.9534702301025391s
Currency | Creation date check for English Heritage Monument Types Thesaurus took 1.4736995697021484s
Currency | Modification date check for English Heritage Monument Types Thesaurus took 1.4045617580413818s
Rep.Conc. | URIs length for English Heritage Monument Types Thesaurus took 1.1657874584197998s
Interoperability | New vocabularies check for English Heritage Monument Types Thesaurus took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Monument Types Thesaurus took 0.8707334995269775s
Accuracy | Check Functional Property for English Heritage Monument Types Thesaurus took 0.5667047500610352s
Accuracy | Check Inverse Functional Property for English Heritage Monument Types Thesaurus took 0.6764662265777588s
Consistency | Disjoint class check for English Heritage Monument Types Thesaurus took 0.45462727546691895s
Consistency | Check Ontology hijacking for English Heritage Monument Types Thesaurus took 0.6944403648376465s
Consistency | Check Invalid usage of undefined properties for English Heritage Monument Types Thesaurus took 3.314647674560547s
Conciseness | Check Extensional conciseness for English Heritage Monument Types Thesaurus took 0.0007069110870361328s
Security | Sign check for English Heritage Monument Types Thesaurus took 1.2990739345550537s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.5569131374359131s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Monument Types Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 124.16027116775513s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.735407829284668s
Availability | VoID file availability check for English Heritage Periods List took 4.205815076828003s
Extra | Recovery of all triples for English Heritage Periods List took 0.5944435596466064s
Performance | Total latancy measurement for English Heritage Periods List took 3.002161741256714s
Amount of data | Number of triples check for English Heritage Periods List took 0.743114709854126s
Versatility | Languages check for English Heritage Periods List took 0.46818995475769043s
Interpretability | Number of blank nodes check for English Heritage Periods List took 1.008272647857666s
Security | Check HTTPS for English Heritage Periods List took 0.5589265823364258s
Interpretability | RDF structures check for English Heritage Periods List took 0.4564549922943115s
Versatility | Serialization formats check for English Heritage Periods List took 1.0579090118408203s
Availability | RDF dump link check for English Heritage Periods List took 0.608109712600708s
License | MR license check for English Heritage Periods List took 4.849559783935547s
License | HR license check for English Heritage Periods List took 0.6133310794830322s
Amount of data | Number of property check for English Heritage Periods List took 0.8419935703277588s
Understandability | Number of label check for English Heritage Periods List took 1.1210927963256836s
Understandability | URI regex check for English Heritage Periods List took 1.7796649932861328s
Understandability | Vocabs check for English Heritage Periods List took 0.6699388027191162s
Verifiability | Authors check for English Heritage Periods List took 0.9879014492034912s
Verifiability | Publishers check for English Heritage Periods List took 1.7647063732147217s
Performance | Throughput check for English Heritage Periods List took 14.046397924423218s
Amount of data | Check the number of entities for English Heritage Periods List took 0.00010085105895996094s
Verifiability | Contribs. check for English Heritage Periods List took 0.490246057510376s
Interlinking | sameAs chians check for English Heritage Periods List took 1.1487045288085938s
Interlinking | skos check for English Heritage Periods List took 1.1150593757629395s
Interlinking | skos check for English Heritage Periods List took 0.9500629901885986s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.7460451126098633s
Currency | Creation date check for English Heritage Periods List took 1.6466848850250244s
Currency | Modification date check for English Heritage Periods List took 1.33620285987854s
Rep.Conc. | URIs length for English Heritage Periods List took 1.2125329971313477s
Interoperability | New vocabularies check for English Heritage Periods List took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.8500826358795166s
Accuracy | Check Functional Property for English Heritage Periods List took 0.6575379371643066s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.7804965972900391s
Consistency | Disjoint class check for English Heritage Periods List took 1.7364428043365479s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.6506381034851074s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.7566771507263184s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00013589859008789062s
Security | Sign check for English Heritage Periods List took 0.5837545394897461s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 3.130660057067871s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.022589921951293945s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.600120544433594e-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.33514404296875e-05s
INFO | --- Analysis for english-heritage-periods-list took 103.16709470748901s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.46646952629089355s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0007770061492919922s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.0062942504882812s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.2472445964813232s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.4552466869354248s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.5138537883758545s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.5794980525970459s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 0.2582573890686035s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.11119675636291504s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.2665431499481201s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.22178125381469727s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 48.654706716537476s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.25740623474121094s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.189332246780396s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.8566098213195801s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.3391904830932617s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.44513916969299316s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.22390341758728027s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.25334954261779785s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.3254122734069824s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.735371828079224s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 3.910064697265625e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.2576463222503662s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.32387232780456543s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.34169483184814453s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.22477006912231445s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.17049336433410645s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.1571805477142334s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.38899803161621094s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.360173225402832s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.14280343055725098s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.13966965675354004s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.205186128616333s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.2407999038696289s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.5722489356994629s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 0.9471135139465332s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.3816616535186768s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.00013709068298339844s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.3371114730834961s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.20958852767944336s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 29.780364990234375s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.57763671875e-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 1.0251998901367188e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 1006.0092468261719s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.147979736328125s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.00049591064453125s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 0.9588251113891602s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.9346272945404053s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.14700627326965332s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.9218251705169678s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.3544175624847412s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 0.12272858619689941s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.1668229103088379s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.1465141773223877s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.14142346382141113s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 46.547120571136475s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.20755457878112793s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.180119276046753s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.1495962142944336s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.12559127807617188s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.3992788791656494s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.1232442855834961s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.14364933967590332s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.19741058349609375s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.510825872421265s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 9.632110595703125e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.2137918472290039s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.15173697471618652s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.2133491039276123s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.1495199203491211s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.1459805965423584s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.1489410400390625s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.2489471435546875s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.2029798030853271s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.1419694423675537s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.21529912948608398s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.13550662994384766s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.13845181465148926s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.4610321521759033s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.600348711013794s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.464684247970581s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00013589859008789062s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.3183574676513672s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.22161555290222168s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 154.9033260345459s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.02669811248779297s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 1.0013580322265625e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 998.3114237785339s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 0.20595049858093262s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0006761550903320312s
Extra | Recovery of all triples for English Indices of Multiple Deprivation took 1.3572578430175781s
Performance | Total latancy measurement for English Indices of Multiple Deprivation took 1.2282195091247559s
Amount of data | Number of triples check for English Indices of Multiple Deprivation took 0.1412334442138672s
Interoperability | New terms check for English Indices of Multiple Deprivation took 1.5076003074645996s
Versatility | Languages check for English Indices of Multiple Deprivation took 0.44374990463256836s
Interpretability | Number of blank nodes check for English Indices of Multiple Deprivation took 0.15613627433776855s
Security | Check HTTPS for English Indices of Multiple Deprivation took 0.1819295883178711s
Interpretability | RDF structures check for English Indices of Multiple Deprivation took 0.2338109016418457s
Versatility | Serialization formats check for English Indices of Multiple Deprivation took 0.14055275917053223s
Availability | RDF dump link check for English Indices of Multiple Deprivation took 46.06103205680847s
License | MR license check for English Indices of Multiple Deprivation took 0.2344207763671875s
License | HR license check for English Indices of Multiple Deprivation took 30.236091136932373s
Amount of data | Number of property check for English Indices of Multiple Deprivation took 0.23205113410949707s
Understandability | Number of label check for English Indices of Multiple Deprivation took 0.2221689224243164s
Understandability | URI regex check for English Indices of Multiple Deprivation took 0.2784581184387207s
Understandability | Vocabs check for English Indices of Multiple Deprivation took 0.14893221855163574s
Verifiability | Authors check for English Indices of Multiple Deprivation took 0.19558334350585938s
Verifiability | Publishers check for English Indices of Multiple Deprivation took 0.20452237129211426s
Performance | Throughput check for English Indices of Multiple Deprivation took 11.033230543136597s
Amount of data | Check the number of entities for English Indices of Multiple Deprivation took 3.981590270996094e-05s
Verifiability | Contribs. check for English Indices of Multiple Deprivation took 0.2021942138671875s
Interlinking | sameAs chians check for English Indices of Multiple Deprivation took 0.21565556526184082s
Interlinking | skos check for English Indices of Multiple Deprivation took 0.21317553520202637s
Interlinking | skos check for English Indices of Multiple Deprivation took 0.14197039604187012s
Timeliness | dataset update frequency check for English Indices of Multiple Deprivation took 0.1324758529663086s
Currency | Creation date check for English Indices of Multiple Deprivation took 0.20061731338500977s
Currency | Modification date check for English Indices of Multiple Deprivation took 0.3398585319519043s
Rep.Conc. | URIs length for English Indices of Multiple Deprivation took 1.1644401550292969s
Interoperability | New vocabularies check for English Indices of Multiple Deprivation took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for English Indices of Multiple Deprivation took 0.14769768714904785s
Accuracy | Check Functional Property for English Indices of Multiple Deprivation took 0.18819808959960938s
Accuracy | Check Inverse Functional Property for English Indices of Multiple Deprivation took 0.14091229438781738s
Consistency | Disjoint class check for English Indices of Multiple Deprivation took 0.14876055717468262s
Consistency | Check Misplaced properties for English Indices of Multiple Deprivation took 1.0100038051605225s
Consistency | Check Ontology hijacking for English Indices of Multiple Deprivation took 0.9649744033813477s
Consistency | Check Invalid usage of undefined properties for English Indices of Multiple Deprivation took 1.4804532527923584s
Conciseness | Check Extensional conciseness for English Indices of Multiple Deprivation took 0.00015664100646972656s
Conciseness | Check Intensional conciseness for English Indices of Multiple Deprivation took 0.2363276481628418s
Security | Sign check for English Indices of Multiple Deprivation took 0.13973689079284668s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 13.457714796066284s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.022462129592895508s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 4.0531158447265625e-05s
Interoperability | Check the re-using of existing vocabs for English Indices of Multiple Deprivation took 1.430511474609375e-06s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 1.1444091796875e-05s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 648.1753413677216s
Availability | SPARQL endpoint availability check for English WordNet took 0.00010180473327636719s
Availability | VoID file availability check for English WordNet took 0.0008571147918701172s
Completeness | Calculation of interlinking completeness for English WordNet took 27.599485874176025s
Reputation | Calculation of the PageRank for English WordNet took 0.021261930465698242s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.933906555175781e-05s
Believability | Calculation of trust value for English WordNet took 1.1444091796875e-05s
INFO | --- Analysis for english-wordnet took 86.14597868919373s
Availability | SPARQL endpoint availability check for English Heritage Places took 6.503680944442749s
Availability | VoID file availability check for English Heritage Places took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for English Heritage Places took 34.89320969581604s
Reputation | Calculation of the PageRank for English Heritage Places took 0.02097487449645996s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Places took 1.0967254638671875e-05s
INFO | --- Analysis for englishheritage_places took 96.25099539756775s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.0890955924987793s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 37.749595403671265s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.021183013916015625s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 0.0001010894775390625s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.1920928955078125e-05s
INFO | --- Analysis for enipedia took 123.66120219230652s
Availability | SPARQL endpoint availability check for Enslaved.org took 8.821487426757812e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Enslaved.org took 1.6805176734924316s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02277684211730957s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.000980377197265625s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.504753112792969e-05s
Believability | Calculation of trust value for Enslaved.org took 1.239776611328125e-05s
INFO | --- Analysis for enslaved.org took 67.65796518325806s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.2761552333831787s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 59.44589877128601s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.02121710777282715s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 6.127357482910156e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.0728836059570312e-05s
INFO | --- Analysis for entice-graph took 121.1304202079773s
Availability | SPARQL endpoint availability check for Entrez Gene took 9.059906005859375e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008020401000976562s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.313859224319458s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02115035057067871s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.838539123535156e-05s
Believability | Calculation of trust value for Entrez Gene took 1.2159347534179688e-05s
INFO | --- Analysis for entrez_gene took 87.73496699333191s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 8.58306884765625e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 180.20451617240906s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.021284103393554688s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.647804260253906e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 1.2636184692382812e-05s
INFO | --- Analysis for entrez_gene_extract took 621.365400314331s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 0.7654480934143066s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.6958155632019043s
Extra | Recovery of all triples for Environment Agency Bathing Water Quality took 24.72401189804077s
Performance | Total latancy measurement for Environment Agency Bathing Water Quality took 1.7758128643035889s
Amount of data | Number of triples check for Environment Agency Bathing Water Quality took 14.782453775405884s
Interoperability | New terms check for Environment Agency Bathing Water Quality took 3.0478477478027344s
Versatility | Languages check for Environment Agency Bathing Water Quality took 40.33391094207764s
Interpretability | Number of blank nodes check for Environment Agency Bathing Water Quality took 12.431438684463501s
Security | Check HTTPS for Environment Agency Bathing Water Quality took 0.29526448249816895s
Interpretability | RDF structures check for Environment Agency Bathing Water Quality took 0.3721961975097656s
Versatility | Serialization formats check for Environment Agency Bathing Water Quality took 0.3405282497406006s
Availability | RDF dump link check for Environment Agency Bathing Water Quality took 22514.45583343506s
License | MR license check for Environment Agency Bathing Water Quality took 0.3551046848297119s
License | HR license check for Environment Agency Bathing Water Quality took 20.350531339645386s
Amount of data | Number of property check for Environment Agency Bathing Water Quality took 0.3691380023956299s
Understandability | Number of label check for Environment Agency Bathing Water Quality took 1.1111993789672852s
Understandability | URI regex check for Environment Agency Bathing Water Quality took 0.7080278396606445s
Understandability | Vocabs check for Environment Agency Bathing Water Quality took 0.4795992374420166s
Verifiability | Authors check for Environment Agency Bathing Water Quality took 0.34675168991088867s
Verifiability | Publishers check for Environment Agency Bathing Water Quality took 0.3807377815246582s
Performance | Throughput check for Environment Agency Bathing Water Quality took 10.772801637649536s
Amount of data | Check the number of entities for Environment Agency Bathing Water Quality took 27.52955198287964s
Verifiability | Contribs. check for Environment Agency Bathing Water Quality took 0.34683966636657715s
Interlinking | sameAs chians check for Environment Agency Bathing Water Quality took 0.343961238861084s
Interlinking | skos check for Environment Agency Bathing Water Quality took 0.32746338844299316s
Interlinking | skos check for Environment Agency Bathing Water Quality took 0.3713970184326172s
Timeliness | dataset update frequency check for Environment Agency Bathing Water Quality took 0.3238201141357422s
Currency | Creation date check for Environment Agency Bathing Water Quality took 0.8748722076416016s
Currency | Modification date check for Environment Agency Bathing Water Quality took 0.4459226131439209s
Rep.Conc. | URIs length for Environment Agency Bathing Water Quality took 49.83456516265869s
Interoperability | New vocabularies check for Environment Agency Bathing Water Quality took 294.84433698654175s
Consistency | Deprecated classes/propertiers check for Environment Agency Bathing Water Quality took 0.42124438285827637s
Accuracy | Check Functional Property for Environment Agency Bathing Water Quality took 0.33818554878234863s
Accuracy | Check Inverse Functional Property for Environment Agency Bathing Water Quality took 0.33195018768310547s
Accuracy | Check Empty annotation labels for Environment Agency Bathing Water Quality took 31.987269639968872s
Accuracy | Check White space in annotation for Environment Agency Bathing Water Quality took 2.3833916187286377s
Accuracy | Check Datatype consistency for Environment Agency Bathing Water Quality took 5.079122543334961s
Consistency | Disjoint class check for Environment Agency Bathing Water Quality took 0.3579549789428711s
Consistency | Check Misplaced properties for Environment Agency Bathing Water Quality took 20.99046540260315s
Consistency | Check Ontology hijacking for Environment Agency Bathing Water Quality took 47.98580741882324s
Consistency | Check Invalid usage of undefined classes for Environment Agency Bathing Water Quality took 1.3246543407440186s
Consistency | Check Invalid usage of undefined properties for Environment Agency Bathing Water Quality took 22.264829635620117s
Conciseness | Check Extensional conciseness for Environment Agency Bathing Water Quality took 3.2664332389831543s
Conciseness | Check Intensional conciseness for Environment Agency Bathing Water Quality took 0.3828716278076172s
Security | Sign check for Environment Agency Bathing Water Quality took 0.34914493560791016s
Availability | Check URIs Dereferenciability for Environment Agency Bathing Water Quality took 4.577902317047119s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 23.15512442588806s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.412101745605469e-05s
Interoperability | Check the re-using of existing vocabs for Environment Agency Bathing Water Quality took 281.0874788761139s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 1.1444091796875e-05s
INFO | --- Analysis for environment-agency-bathing-water-quality took 24592.292086601257s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.3982565402984619s
Availability | VoID file availability check for environment.data.gov.uk took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 180.20083856582642s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.022076845169067383s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 6.29425048828125e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 8.821487426757812e-06s
INFO | --- Analysis for environment-data-gov-uk took 847.8341917991638s
Availability | SPARQL endpoint availability check for EARTh took 271.4286136627197s
Availability | VoID file availability check for EARTh took 3.922283411026001s
Completeness | Calculation of interlinking completeness for EARTh took 0.4732487201690674s
Reputation | Calculation of the PageRank for EARTh took 0.02124476432800293s
Interlinking | Calculation of Degree of Connection for EARTh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00011110305786132812s
Interoperability | Check the re-using of existing vocabs for EARTh took 17.162675857543945s
Believability | Calculation of trust value for EARTh took 1.33514404296875e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 494.9692268371582s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.6371595859527588s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0005970001220703125s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 107.61629390716553s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.9570724964141846s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.385507345199585s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 13.916579246520996s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.2032792568207s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.4400477409362793s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.2970132827758789s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 0.6265382766723633s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.31783008575439453s
License | MR license check for Micka (EO metadata) @PSNC took 0.6940619945526123s
License | HR license check for Micka (EO metadata) @PSNC took 300.2101411819458s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.20257568359375s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.7000904083251953s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 1.1834344863891602s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.5097038745880127s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.21346664428710938s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 3.0555577278137207s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.247307538986206s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 8.678436279296875e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.18202543258666992s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.19635748863220215s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.49712085723876953s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.42522501945495605s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 0.7647433280944824s
Currency | Creation date check for Micka (EO metadata) @PSNC took 1.156921625137329s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.263521671295166s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 156.35569167137146s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.19788789749145508s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.4310884475708008s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.4712207317352295s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 33.22515535354614s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.7275350093841553s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.656977415084839s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.18564701080322266s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 87.65662455558777s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.698678016662598s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 32.47253751754761s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.2423253059387207s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 86.83485460281372s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 3.0154387950897217s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.4800446033477783s
Security | Sign check for Micka (EO metadata) @PSNC took 1.051711082458496s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 13.680261135101318s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 1.1858747005462646s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021962881088256836s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 5.4836273193359375e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for EO_metadata took 2269.9079461097717s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 9.584426879882812e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 179.67260336875916s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.022171735763549805s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 4.00543212890625e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.8835067749023438e-05s
INFO | --- Analysis for EOKP-Datasets took 434.5146141052246s
Availability | SPARQL endpoint availability check for EPA-CDR took 9.608268737792969e-05s
Availability | VoID file availability check for EPA-CDR took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for EPA-CDR took 8.599894762039185s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02161884307861328s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 4.029273986816406e-05s
Believability | Calculation of trust value for EPA-CDR took 9.059906005859375e-06s
INFO | --- Analysis for epa-cdr took 313.03616881370544s
Availability | SPARQL endpoint availability check for EPA-FRS took 9.965896606445312e-05s
Availability | VoID file availability check for EPA-FRS took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for EPA-FRS took 60.06808924674988s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02179551124572754s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 8.702278137207031e-05s
Believability | Calculation of trust value for EPA-FRS took 1.2159347534179688e-05s
INFO | --- Analysis for epa-frs took 434.9096682071686s
Availability | SPARQL endpoint availability check for EPA-RCRA took 5.269050598144531e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0007727146148681641s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 109.78834819793701s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.023279905319213867s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 4.887580871582031e-05s
Believability | Calculation of trust value for EPA-RCRA took 9.298324584960938e-06s
INFO | --- Analysis for epa-rcra took 595.289618730545s
Availability | SPARQL endpoint availability check for EPA-SRS took 8.96453857421875e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for EPA-SRS took 100.71861696243286s
Reputation | Calculation of the PageRank for EPA-SRS took 0.022658586502075195s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 8.106231689453125e-05s
Believability | Calculation of trust value for EPA-SRS took 1.4543533325195312e-05s
INFO | --- Analysis for epa-srs took 285.20895886421204s
Availability | SPARQL endpoint availability check for EPA-TRI took 9.322166442871094e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.3538804054260254s
Reputation | Calculation of the PageRank for EPA-TRI took 0.021625041961669922s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.52587890625e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.4332275390625e-05s
Believability | Calculation of trust value for EPA-TRI took 1.9550323486328125e-05s
INFO | --- Analysis for epa-tri took 364.961945772171s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 8.726119995117188e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 175.62489199638367s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.022024154663085938s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 8.392333984375e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 1.71661376953125e-05s
INFO | --- Analysis for epo took 673.5300035476685s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.06118416786193848s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 57.3289794921875s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.021876811981201172s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0009424686431884766s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00015497207641601562s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 152.0518627166748s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5381309986114502s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 60.35761737823486s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.021177291870117188s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 9.250640869140625e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.1920928955078125e-05s
INFO | --- Analysis for eprtr took 240.84817266464233s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.4987523555755615s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0006215572357177734s
Extra | Recovery of all triples for Railway Infrastructure KG took 59.90283560752869s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.2338814735412598s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.25969600677490234s
Interoperability | New terms check for Railway Infrastructure KG took 1.5547676086425781s
Versatility | Languages check for Railway Infrastructure KG took 81.64003992080688s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.2811861038208008s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.9164700508117676s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.502028226852417s
Availability | RDF dump link check for Railway Infrastructure KG took 0.2655453681945801s
License | MR license check for Railway Infrastructure KG took 1.2268595695495605s
License | HR license check for Railway Infrastructure KG took 65.88785076141357s
Amount of data | Number of property check for Railway Infrastructure KG took 0.28168368339538574s
Understandability | Number of label check for Railway Infrastructure KG took 0.6230068206787109s
Understandability | URI regex check for Railway Infrastructure KG took 0.5645318031311035s
Understandability | Vocabs check for Railway Infrastructure KG took 0.35541820526123047s
Verifiability | Authors check for Railway Infrastructure KG took 0.22052979469299316s
Verifiability | Publishers check for Railway Infrastructure KG took 0.3388960361480713s
Performance | Throughput check for Railway Infrastructure KG took 11.645777702331543s
Amount of data | Check the number of entities for Railway Infrastructure KG took 0.00010275840759277344s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.24724173545837402s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.24448013305664062s
Interlinking | skos check for Railway Infrastructure KG took 0.23485112190246582s
Interlinking | skos check for Railway Infrastructure KG took 0.2131941318511963s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.23150396347045898s
Currency | Creation date check for Railway Infrastructure KG took 0.24966835975646973s
Currency | Modification date check for Railway Infrastructure KG took 0.2536194324493408s
Rep.Conc. | URIs length for Railway Infrastructure KG took 22.70867395401001s
Interoperability | New vocabularies check for Railway Infrastructure KG took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.22126150131225586s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.308788537979126s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.3194711208343506s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 18.671297311782837s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 3.2572574615478516s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.689863681793213s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.3118002414703369s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.6310491561889648s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.834168195724487s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 19.140414237976074s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.3930168151855469s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.6188066005706787s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 3.1246066093444824s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.4047887325286865s
Security | Sign check for Railway Infrastructure KG took 0.2290647029876709s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2351.0579273700714s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.9961891174316406s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.02364349365234375s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0008924007415771484s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 0.00015997886657714844s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 1.6689300537109375e-06s
Believability | Calculation of trust value for Railway Infrastructure KG took 8.106231689453125e-06s
INFO | --- Analysis for ERAKG took 2935.5577697753906s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.22479867935180664s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 3.258472442626953s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.021192312240600586s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.218650817871094e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 9.059906005859375e-06s
INFO | --- Analysis for es-msssi-drug-prices took 11.64272928237915s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 8.869171142578125e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 2.1760339736938477s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02153301239013672s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 2.288818359375e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0009355545043945312s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 0.00011348724365234375s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 8.821487426757812e-06s
INFO | --- Analysis for esd-standards took 13.100141525268555s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 0.00011086463928222656s
Availability | VoID file availability check for ESD-Toolkit took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 2.023195505142212s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.04116678237915039s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.001169443130493164s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 9.107589721679688e-05s
Believability | Calculation of trust value for ESD-Toolkit took 8.344650268554688e-06s
INFO | --- Analysis for esd-toolkit took 11.28241229057312s
Availability | SPARQL endpoint availability check for Dataset Esis took 9.083747863769531e-05s
Availability | VoID file availability check for Dataset Esis took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.615757942199707s
Reputation | Calculation of the PageRank for Dataset Esis took 0.02084970474243164s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 2.956390380859375e-05s
Believability | Calculation of trust value for Dataset Esis took 1.3589859008789062e-05s
INFO | --- Analysis for esislearning took 10.625151872634888s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 0.00010967254638671875s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 2.1831252574920654s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.147125244140625e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.4066696166992188e-05s
INFO | --- Analysis for ESV took 7.991894721984863s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6337685585021973s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.54422926902771s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 7.2776939868927s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 2.2802631855010986s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.00035881996154785156s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.5709354877471924s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.021289825439453125s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.891654968261719e-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.604448556900024s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 8.845329284667969e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.8106050491333008s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.021270036697387695s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 2.9802322387695312e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 7.3909759521484375e-06s
INFO | --- Analysis for eu-dgt-tm took 6.79277229309082s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.96453857421875e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 1.9791693687438965s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 1.6840131282806396s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.02388453483581543s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.43865966796875e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 9.775161743164062e-06s
INFO | --- Analysis for eu-institutions took 11.498328685760498s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.0284759998321533s
Availability | VoID file availability check for EU Parliament Media Library took 1.7507116794586182s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 1.6296272277832031s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020941972732543945s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.4809112548828125e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 9.775161743164062e-06s
INFO | --- Analysis for eu-parliament-media took 13.41062593460083s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.225492238998413s
Availability | VoID file availability check for EU Who Is Who took 1.6153395175933838s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 1.1363682746887207s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.719329833984375e-05s
Believability | Calculation of trust value for EU Who Is Who took 8.58306884765625e-06s
INFO | --- Analysis for eu-who-is-who took 18.85426092147827s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.9922327995300293s
Availability | VoID file availability check for EUMIDA as Linked Data took 1.8562324047088623s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.3420746326446533s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.029273986816406e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for eumida-linked-data took 15.222294807434082s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3619978427886963s
Availability | VoID file availability check for European Nature Information System took 0.576859712600708s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.43836021423339844s
Reputation | Calculation of the PageRank for European Nature Information System took 0.021425485610961914s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010991096496582031s
Interoperability | Check the re-using of existing vocabs for European Nature Information System took 46.40599179267883s
Believability | Calculation of trust value for European Nature Information System took 1.3828277587890625e-05s
INFO | --- Analysis for eunis took 53.850242614746094s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 3.071295976638794s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.000873565673828125s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.9250683784484863s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.025296926498413086s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0011284351348876953s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 0.00010609626770019531s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for eur-lex-rdf took 14.76994252204895s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.1557729244232178s
Availability | VoID file availability check for Standard Eurobarometer took 1.6837661266326904s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.6067347526550293s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02115917205810547s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.315376281738281e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 9.059906005859375e-06s
INFO | --- Analysis for eurobarometer-standard took 21.04521346092224s
Availability | SPARQL endpoint availability check for European Election Results took 1.0430223941802979s
Availability | VoID file availability check for European Election Results took 1.7004146575927734s
Completeness | Calculation of interlinking completeness for European Election Results took 1.182666301727295s
Reputation | Calculation of the PageRank for European Election Results took 0.021973133087158203s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.001264333724975586s
Interlinking | Calculation of Clustering coefficient for European Election Results took 4.744529724121094e-05s
Believability | Calculation of trust value for European Election Results took 9.5367431640625e-06s
INFO | --- Analysis for european-election-results took 13.041099071502686s
Availability | SPARQL endpoint availability check for EPO patents took 0.3303382396697998s
Availability | VoID file availability check for EPO patents took 0.0006074905395507812s
Extra | Recovery of all triples for EPO patents took 25.69474768638611s
Performance | Total latancy measurement for EPO patents took 0.6534371376037598s
Amount of data | Number of triples check for EPO patents took 90.25895977020264s
Versatility | Languages check for EPO patents took 120.09076285362244s
Interpretability | Number of blank nodes check for EPO patents took 90.27724504470825s
Interpretability | RDF structures check for EPO patents took 0.1470808982849121s
Versatility | Serialization formats check for EPO patents took 0.15093088150024414s
Availability | RDF dump link check for EPO patents took 0.11513638496398926s
License | MR license check for EPO patents took 0.11181783676147461s
License | HR license check for EPO patents took 90.22344899177551s
Amount of data | Number of property check for EPO patents took 0.13335776329040527s
Understandability | Number of label check for EPO patents took 90.22841119766235s
Understandability | URI regex check for EPO patents took 0.2761678695678711s
Understandability | Vocabs check for EPO patents took 0.14732575416564941s
Verifiability | Authors check for EPO patents took 0.12830901145935059s
Verifiability | Publishers check for EPO patents took 0.09759283065795898s
Performance | Throughput check for EPO patents took 10.628564357757568s
Amount of data | Check the number of entities for EPO patents took 0.0006589889526367188s
Verifiability | Contribs. check for EPO patents took 0.11825752258300781s
Interlinking | sameAs chians check for EPO patents took 0.11428618431091309s
Interlinking | skos check for EPO patents took 0.12328600883483887s
Interlinking | skos check for EPO patents took 0.15926718711853027s
Timeliness | dataset update frequency check for EPO patents took 0.10266351699829102s
Currency | Creation date check for EPO patents took 0.12632060050964355s
Currency | Modification date check for EPO patents took 0.874225378036499s
Rep.Conc. | URIs length for EPO patents took 149.75317788124084s
Interoperability | New vocabularies check for EPO patents took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.137099027633667s
Accuracy | Check Empty annotation labels for EPO patents took 14.863359451293945s
Accuracy | Check White space in annotation for EPO patents took 3.043574571609497s
Accuracy | Check Datatype consistency for EPO patents took 5.078969955444336s
Consistency | Disjoint class check for EPO patents took 0.09793472290039062s
Consistency | Check Misplaced properties for EPO patents took 120.25129079818726s
Consistency | Check Ontology hijacking for EPO patents took 17.99911594390869s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.6655266284942627s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.58253693580627s
Conciseness | Check Extensional conciseness for EPO patents took 3.037292718887329s
Conciseness | Check Intensional conciseness for EPO patents took 0.15247416496276855s
Security | Sign check for EPO patents took 0.13164162635803223s
Availability | Check URIs Dereferenciability for EPO patents took 1.0650029182434082s
Completeness | Calculation of interlinking completeness for EPO patents took 0.48993444442749023s
Reputation | Calculation of the PageRank for EPO patents took 0.022655725479125977s
Interlinking | Calculation of Degree of Connection for EPO patents took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0010187625885009766s
Interlinking | Calculation of Clustering coefficient for EPO patents took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 2.6226043701171875e-06s
Believability | Calculation of trust value for EPO patents took 1.6927719116210938e-05s
INFO | --- Analysis for European_Patent_Information took 1625.0595474243164s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 8.559226989746094e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0008032321929931641s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.3057868480682373s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.02137017250061035s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 4.220008850097656e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for europeana-lod took 422.3979299068451s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 9.083747863769531e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.19353199005126953s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.7877087593078613s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.021160125732421875s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 0.00010943412780761719s
Interoperability | Check the re-using of existing vocabs for Europeana Linked Open Data V1.0 took 149.28654956817627s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.3909759521484375e-06s
INFO | --- Analysis for europeana-lod-v1 took 297.2967848777771s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.3495354652404785s
Availability | VoID file availability check for Europeana SPARQL took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.35585451126098633s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.021115779876708984s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.936622619628906e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.9788742065429688e-05s
INFO | --- Analysis for europeana-sparql took 123.78721022605896s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.06993556022644043s
Availability | VoID file availability check for EuroSentiment took 0.0003447532653808594s
Completeness | Calculation of interlinking completeness for EuroSentiment took 119.72022938728333s
Reputation | Calculation of the PageRank for EuroSentiment took 0.022323131561279297s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.52587890625e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.315376281738281e-05s
Believability | Calculation of trust value for EuroSentiment took 1.2159347534179688e-05s
INFO | --- Analysis for eurosentiment took 181.3961319923401s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.673004150390625e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 179.52020001411438s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.023494243621826172s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0011262893676757812s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 0.00011277198791503906s
Believability | Calculation of trust value for Eurostat RDF datasets took 1.52587890625e-05s
INFO | --- Analysis for eurostat-rdf took 733.2853319644928s
Availability | SPARQL endpoint availability check for EuroVoc took 0.22832632064819336s
Availability | VoID file availability check for EuroVoc took 0.0007698535919189453s
Extra | Recovery of all triples for EuroVoc took 162.96242094039917s
Amount of data | Number of triples check for EuroVoc took 44.65921425819397s
Interoperability | New terms check for EuroVoc took 54.039003133773804s
Versatility | Languages check for EuroVoc took 300.13284158706665s
Interpretability | Number of blank nodes check for EuroVoc took 14.545595169067383s
Security | Check HTTPS for EuroVoc took 0.3441956043243408s
Interpretability | RDF structures check for EuroVoc took 0.34952497482299805s
Versatility | Serialization formats check for EuroVoc took 0.35089588165283203s
Availability | RDF dump link check for EuroVoc took 0.2636408805847168s
License | MR license check for EuroVoc took 0.4562251567840576s
License | HR license check for EuroVoc took 300.03108167648315s
Amount of data | Number of property check for EuroVoc took 0.17192745208740234s
Understandability | Number of label check for EuroVoc took 2.206875801086426s
Understandability | URI regex check for EuroVoc took 0.37512993812561035s
Understandability | Vocabs check for EuroVoc took 0.11071610450744629s
Verifiability | Authors check for EuroVoc took 0.2788419723510742s
Verifiability | Publishers check for EuroVoc took 0.18743348121643066s
Performance | Throughput check for EuroVoc took 10.489635705947876s
Amount of data | Check the number of entities for EuroVoc took 0.0005741119384765625s
Verifiability | Contribs. check for EuroVoc took 0.1905992031097412s
Interlinking | sameAs chians check for EuroVoc took 6.407199144363403s
Interlinking | skos check for EuroVoc took 0.33071446418762207s
Interlinking | skos check for EuroVoc took 0.28905701637268066s
Timeliness | dataset update frequency check for EuroVoc took 0.14136385917663574s
Currency | Creation date check for EuroVoc took 0.937786340713501s
Currency | Modification date check for EuroVoc took 0.12723803520202637s
Rep.Conc. | URIs length for EuroVoc took 415.9882216453552s
Interoperability | New vocabularies check for EuroVoc took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.1598832607269287s
Accuracy | Check Functional Property for EuroVoc took 0.19220995903015137s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.16211700439453125s
Accuracy | Check Empty annotation labels for EuroVoc took 41.474104166030884s
Accuracy | Check White space in annotation for EuroVoc took 3.089000701904297s
Accuracy | Check Datatype consistency for EuroVoc took 2.8008921146392822s
Consistency | Disjoint class check for EuroVoc took 0.13386082649230957s
Consistency | Check Misplaced properties for EuroVoc took 293.6450366973877s
Consistency | Misplaced classes for EuroVoc took 8.043801069259644s
Consistency | Check Ontology hijacking for EuroVoc took 53.03609919548035s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.744307279586792s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 298.6003620624542s
Conciseness | Check Extensional conciseness for EuroVoc took 2.9477174282073975s
Conciseness | Check Intensional conciseness for EuroVoc took 0.357438325881958s
Security | Sign check for EuroVoc took 0.41100382804870605s
Availability | Check URIs Dereferenciability for EuroVoc took 7.682939052581787s
Completeness | Calculation of interlinking completeness for EuroVoc took 93.49357008934021s
Reputation | Calculation of the PageRank for EuroVoc took 0.02673816680908203s
Interlinking | Calculation of Degree of Connection for EuroVoc took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0009124279022216797s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 0.00010180473327636719s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 2.1457672119140625e-06s
Believability | Calculation of trust value for EuroVoc took 1.2874603271484375e-05s
INFO | --- Analysis for eurovoc took 10104.432556390762s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 30.342397451400757s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 3.0373218059539795s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.0211026668548584s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 3.9577484130859375e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 1.239776611328125e-05s
INFO | --- Analysis for eurovoc-in-skos took 48.10119152069092s
Availability | SPARQL endpoint availability check for European Television Heritage took 2.0608713626861572s
Availability | VoID file availability check for European Television Heritage took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.32265353202819824s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 3.314018249511719e-05s
Believability | Calculation of trust value for European Television Heritage took 1.2636184692382812e-05s
INFO | --- Analysis for euscreen took 7.251054048538208s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 9.036064147949219e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.7646579742431641s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.021176576614379883s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.887580871582031e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 9.775161743164062e-06s
INFO | --- Analysis for euskadi-farmacias took 8.150856733322144s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.6986291408538818s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.5905020236968994s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.021361827850341797s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0010344982147216797s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.7670135498046875e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.33514404296875e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.4300315380096436s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.5291850566864014s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.9108834266662598s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.462501525878906e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.3589859008789062e-05s
INFO | --- Analysis for eutc-productions took 8.57139778137207s
Availability | SPARQL endpoint availability check for EventMedia took 0.41776061058044434s
Availability | VoID file availability check for EventMedia took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for EventMedia took 0.46155238151550293s
Reputation | Calculation of the PageRank for EventMedia took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for EventMedia took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EventMedia took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00013589859008789062s
Believability | Calculation of trust value for EventMedia took 1.2159347534179688e-05s
INFO | --- Analysis for event-media took 21.343136072158813s
Availability | SPARQL endpoint availability check for EventKG took 8.916854858398438e-05s
Availability | VoID file availability check for EventKG took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for EventKG took 0.8547573089599609s
Reputation | Calculation of the PageRank for EventKG took 0.023867368698120117s
Interlinking | Calculation of Degree of Connection for EventKG took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0013775825500488281s
Interlinking | Calculation of Clustering coefficient for EventKG took 0.00013136863708496094s
Believability | Calculation of trust value for EventKG took 8.106231689453125e-06s
INFO | --- Analysis for eventkg took 3.800203323364258s
Availability | SPARQL endpoint availability check for Eventseer took 1.8377125263214111s
Availability | VoID file availability check for Eventseer took 0.0003936290740966797s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2910761833190918s
Reputation | Calculation of the PageRank for Eventseer took 0.0223696231842041s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0010895729064941406s
Interlinking | Calculation of Clustering coefficient for Eventseer took 6.29425048828125e-05s
Believability | Calculation of trust value for Eventseer took 1.1920928955078125e-05s
INFO | --- Analysis for eventseer took 3.8634188175201416s
Availability | SPARQL endpoint availability check for Face Link took 8.940696716308594e-05s
Availability | VoID file availability check for Face Link took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Face Link took 0.4312782287597656s
Reputation | Calculation of the PageRank for Face Link took 0.02924346923828125s
Interlinking | Calculation of Degree of Connection for Face Link took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0015459060668945312s
Interlinking | Calculation of Clustering coefficient for Face Link took 6.67572021484375e-05s
Believability | Calculation of trust value for Face Link took 1.1920928955078125e-05s
INFO | --- Analysis for Face_Link took 6.075457572937012s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 9.799003601074219e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.3186330795288086s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.02258586883544922s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0011448860168457031s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 4.3392181396484375e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 8.344650268554688e-06s
INFO | --- Analysis for facebook-lids took 2.4325292110443115s
Availability | SPARQL endpoint availability check for Fact Forge took 0.44028544425964355s
Availability | VoID file availability check for Fact Forge took 0.00039839744567871094s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.30808472633361816s
Reputation | Calculation of the PageRank for Fact Forge took 0.021600723266601562s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0010058879852294922s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.7670135498046875e-05s
Believability | Calculation of trust value for Fact Forge took 8.821487426757812e-06s
INFO | --- Analysis for fact-forge took 2.709577798843384s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5757594108581543s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0003962516784667969s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 130.2544584274292s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.2451794147491455s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.868793487548828s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.115833282470703s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.3557572364807s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.3489792346954346s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.25734782218933105s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5163149833679199s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.27403903007507324s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4611985683441162s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.16833782196045s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6382884979248047s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.709554672241211s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0322422981262207s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.429440975189209s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19248366355895996s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.9049911499023438s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 13.811804294586182s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.630752563476562e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21153879165649414s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19688868522644043s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.508718729019165s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4297325611114502s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6417579650878906s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.9683184623718262s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.24399805068969727s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 160.46490287780762s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2156369686126709s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.436779260635376s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3648414611816406s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 41.81520962715149s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7009458541870117s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6572675704956055s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20901751518249512s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 85.71582341194153s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.442628383636475s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 38.07077217102051s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4877212047576904s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 87.75673961639404s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.9800984859466553s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.5910863876342773s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9993410110473633s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 21.085388660430908s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 44.12470364570618s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.021582365036010742s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3113021850585938e-05s
INFO | --- Analysis for FADN_(2019) took 2361.2107498645782s
Availability | SPARQL endpoint availability check for FAMEData took 9.107589721679688e-05s
Availability | VoID file availability check for FAMEData took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for FAMEData took 45.193021297454834s
Reputation | Calculation of the PageRank for FAMEData took 0.022049665451049805s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for FAMEData took 2.8371810913085938e-05s
Believability | Calculation of trust value for FAMEData took 1.2636184692382812e-05s
INFO | --- Analysis for famedata took 263.2896640300751s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 0.00011014938354492188s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 52.040727376937866s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.0213165283203125s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00011897087097167969s
Believability | Calculation of trust value for FAO geopolitical ontology took 1.5974044799804688e-05s
INFO | --- Analysis for fao-geopolitical-ontology took 248.3775155544281s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.10382914543151855s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 37.21045422554016s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.02140045166015625s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010848045349121094s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for fao-linked-data took 225.4832775592804s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.5299530029296875e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.30140113830566406s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.033310890197753906s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0014281272888183594s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 4.935264587402344e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.7404556274414062e-05s
INFO | --- Analysis for FAO_species took 205.9660608768463s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.47692561149597s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.4138803482055664s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02200603485107422s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 5.364418029785156e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.3113021850585938e-05s
INFO | --- Analysis for farmbio-chembl took 237.95452213287354s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 9.369850158691406e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.3346383571624756s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 4.8160552978515625e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 1.1682510375976562e-05s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 244.2022669315338s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 8.535385131835938e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.2965507507324219s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020929336547851562s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for farolapp-dataset took 1.9606688022613525s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.8160552978515625e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.3775327205657959s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.021956920623779297s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 3.886222839355469e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 1.1444091796875e-05s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 159.7886528968811s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.649162292480469e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.3389620780944824s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.021930217742919922s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.0517578125e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.2159347534179688e-05s
INFO | --- Analysis for fatimazahra took 199.55063343048096s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 10.743651628494263s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 49.8235981464386s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.021202802658081055s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 4.267692565917969e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 1.1920928955078125e-05s
INFO | --- Analysis for federal-economic-rdf took 163.3298304080963s
Availability | SPARQL endpoint availability check for Feed Wrapper took 8.940696716308594e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 59.62130284309387s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.02321171760559082s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.409385681152344e-05s
Believability | Calculation of trust value for Feed Wrapper took 1.1920928955078125e-05s
INFO | --- Analysis for feedwrapper-lids took 190.78217124938965s
Availability | SPARQL endpoint availability check for FHIR STU3 took 9.465217590332031e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 39.724785804748535s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.023411273956298828s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0010914802551269531s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 4.649162292480469e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.239776611328125e-05s
INFO | --- Analysis for FHIR_STU3 took 233.19291996955872s
Availability | SPARQL endpoint availability check for FiESTA took 8.702278137207031e-05s
Availability | VoID file availability check for FiESTA took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for FiESTA took 0.4261894226074219s
Reputation | Calculation of the PageRank for FiESTA took 0.02143263816833496s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for FiESTA took 5.1021575927734375e-05s
Believability | Calculation of trust value for FiESTA took 1.0967254638671875e-05s
INFO | --- Analysis for fiesta took 319.08533573150635s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.34600830078125e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.303478479385376s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.021719694137573242s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.552436828613281e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.239776611328125e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 1.9588828086853027s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 0.000118255615234375s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.30927324295043945s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 8.821487426757812e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 1.1682510375976562e-05s
INFO | --- Analysis for finnish-municipalities took 422.8049204349518s
Availability | SPARQL endpoint availability check for firmao took 4.1484832763671875e-05s
Availability | VoID file availability check for firmao took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for firmao took 22.24589490890503s
Reputation | Calculation of the PageRank for firmao took 0.02250385284423828s
Interlinking | Calculation of Degree of Connection for firmao took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for firmao took 4.3392181396484375e-05s
Believability | Calculation of trust value for firmao took 1.33514404296875e-05s
INFO | --- Analysis for firmao took 391.84390330314636s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 0.6306374073028564s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0009086132049560547s
Extra | Recovery of all triples for FISH Archaeological Objects Thesaurus took 0.40369272232055664s
Performance | Total latancy measurement for FISH Archaeological Objects Thesaurus took 1.5871143341064453s
Amount of data | Number of triples check for FISH Archaeological Objects Thesaurus took 0.45687413215637207s
Versatility | Languages check for FISH Archaeological Objects Thesaurus took 0.28565239906311035s
Interpretability | Number of blank nodes check for FISH Archaeological Objects Thesaurus took 0.46413278579711914s
Security | Check HTTPS for FISH Archaeological Objects Thesaurus took 0.2199091911315918s
Interpretability | RDF structures check for FISH Archaeological Objects Thesaurus took 0.26056742668151855s
Versatility | Serialization formats check for FISH Archaeological Objects Thesaurus took 0.3503224849700928s
Availability | RDF dump link check for FISH Archaeological Objects Thesaurus took 0.3901221752166748s
License | MR license check for FISH Archaeological Objects Thesaurus took 0.4314730167388916s
License | HR license check for FISH Archaeological Objects Thesaurus took 0.4619479179382324s
Amount of data | Number of property check for FISH Archaeological Objects Thesaurus took 0.3872978687286377s
Understandability | Number of label check for FISH Archaeological Objects Thesaurus took 0.6561875343322754s
Understandability | URI regex check for FISH Archaeological Objects Thesaurus took 0.6934735774993896s
Understandability | Vocabs check for FISH Archaeological Objects Thesaurus took 0.34100842475891113s
Verifiability | Authors check for FISH Archaeological Objects Thesaurus took 0.35106849670410156s
Verifiability | Publishers check for FISH Archaeological Objects Thesaurus took 0.48808979988098145s
Performance | Throughput check for FISH Archaeological Objects Thesaurus took 12.772928953170776s
Amount of data | Check the number of entities for FISH Archaeological Objects Thesaurus took 9.441375732421875e-05s
Verifiability | Contribs. check for FISH Archaeological Objects Thesaurus took 0.32694220542907715s
Interlinking | sameAs chians check for FISH Archaeological Objects Thesaurus took 0.3423318862915039s
Interlinking | skos check for FISH Archaeological Objects Thesaurus took 0.3707423210144043s
Interlinking | skos check for FISH Archaeological Objects Thesaurus took 0.3711421489715576s
Timeliness | dataset update frequency check for FISH Archaeological Objects Thesaurus took 0.3387274742126465s
Currency | Creation date check for FISH Archaeological Objects Thesaurus took 0.7135944366455078s
Currency | Modification date check for FISH Archaeological Objects Thesaurus took 0.6424179077148438s
Rep.Conc. | URIs length for FISH Archaeological Objects Thesaurus took 0.6283977031707764s
Interoperability | New vocabularies check for FISH Archaeological Objects Thesaurus took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for FISH Archaeological Objects Thesaurus took 0.29877471923828125s
Accuracy | Check Functional Property for FISH Archaeological Objects Thesaurus took 0.27895092964172363s
Accuracy | Check Inverse Functional Property for FISH Archaeological Objects Thesaurus took 0.30667662620544434s
Consistency | Disjoint class check for FISH Archaeological Objects Thesaurus took 0.2887089252471924s
Consistency | Check Ontology hijacking for FISH Archaeological Objects Thesaurus took 0.4582042694091797s
Consistency | Check Invalid usage of undefined properties for FISH Archaeological Objects Thesaurus took 2.3929834365844727s
Conciseness | Check Extensional conciseness for FISH Archaeological Objects Thesaurus took 0.00072479248046875s
Security | Sign check for FISH Archaeological Objects Thesaurus took 0.4850945472717285s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.3707275390625s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.021680116653442383s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for FISH Archaeological Objects Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 548.1101114749908s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.3322596549987793s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005550384521484375s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 128.43873572349548s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 1.9145615100860596s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 9.382544040679932s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.454623222351074s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.1668429374695s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.1225175857543945s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.29173803329467773s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 0.6701617240905762s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 1.3660051822662354s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.7453048229217529s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.2408320903778s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.19838786125183105s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.4985220432281494s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 1.197336196899414s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 1.5373783111572266s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.20688939094543457s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 2.9755022525787354s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 14.074102878570557s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 0.00010037422180175781s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.21048951148986816s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.21138334274291992s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.49666643142700195s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.45383334159851074s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 1.494438886642456s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 1.1886937618255615s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.25209927558898926s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 161.13065767288208s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.1994619369506836s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 1.3960058689117432s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.4465296268463135s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 43.783303022384644s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.700537919998169s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.783970594406128s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.1848468780517578s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 88.04522585868835s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 9.070251703262329s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 45.74236035346985s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.4018478393554688s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 88.28588533401489s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.9712700843811035s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 1.3310503959655762s
Security | Sign check for Norway fishery stocks dataset @PSNC took 1.1361868381500244s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 2.2393457889556885s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.7706999778747559s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.02184915542602539s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2305.6338589191437s
Availability | SPARQL endpoint availability check for Fishes of Texas took 0.00010132789611816406s
Availability | VoID file availability check for Fishes of Texas took 0.0007970333099365234s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 13.958163738250732s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.023318052291870117s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 3.743171691894531e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.001720428466796875s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 0.0003578662872314453s
Believability | Calculation of trust value for Fishes of Texas took 1.239776611328125e-05s
INFO | --- Analysis for fishes-of-texas took 172.60752177238464s
Availability | SPARQL endpoint availability check for flickr? wrappr took 8.988380432128906e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.8034515380859375s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02515125274658203s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0014252662658691406s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 0.00015473365783691406s
Believability | Calculation of trust value for flickr? wrappr took 1.1682510375976562e-05s
INFO | --- Analysis for flickr-wrappr took 42.82052707672119s
Availability | SPARQL endpoint availability check for flickr.person took 8.869171142578125e-05s
Availability | VoID file availability check for flickr.person took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for flickr.person took 4.153697490692139s
Reputation | Calculation of the PageRank for flickr.person took 0.026326656341552734s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.00130462646484375s
Interlinking | Calculation of Clustering coefficient for flickr.person took 6.67572021484375e-05s
Believability | Calculation of trust value for flickr.person took 9.775161743164062e-06s
INFO | --- Analysis for flickr_person took 110.592111825943s
Availability | SPARQL endpoint availability check for flickr.videoobject took 8.797645568847656e-05s
Availability | VoID file availability check for flickr.videoobject took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 34.84082651138306s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.02227783203125s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0011162757873535156s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.7670135498046875e-05s
Believability | Calculation of trust value for flickr.videoobject took 1.1682510375976562e-05s
INFO | --- Analysis for flickr_videoobject took 81.55138778686523s
Availability | SPARQL endpoint availability check for Future land use simulation model took 6.365776062011719e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.29500532150268555s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.021289587020874023s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.170967102050781e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.1682510375976562e-05s
INFO | --- Analysis for FLUS took 166.940495967865s
Availability | SPARQL endpoint availability check for Fly-TED took 9.894371032714844e-05s
Availability | VoID file availability check for Fly-TED took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.29494690895080566s
Reputation | Calculation of the PageRank for Fly-TED took 0.021465063095092773s
Interlinking | Calculation of Degree of Connection for Fly-TED took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 4.100799560546875e-05s
Believability | Calculation of trust value for Fly-TED took 1.239776611328125e-05s
INFO | --- Analysis for fly-ted took 240.573246717453s
Availability | SPARQL endpoint availability check for FlyAtlas took 0.00010585784912109375s
Availability | VoID file availability check for FlyAtlas took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.29233288764953613s
Reputation | Calculation of the PageRank for FlyAtlas took 0.021260976791381836s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.719329833984375e-05s
Believability | Calculation of trust value for FlyAtlas took 7.867813110351562e-06s
INFO | --- Analysis for flyatlas took 120.45908331871033s
Availability | SPARQL endpoint availability check for Flybase took 1.6005113124847412s
Availability | VoID file availability check for Flybase took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Flybase took 0.3227205276489258s
Reputation | Calculation of the PageRank for Flybase took 0.020993947982788086s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.504753112792969e-05s
Believability | Calculation of trust value for Flybase took 1.1444091796875e-05s
INFO | --- Analysis for flybase took 64.2101321220398s
Availability | SPARQL endpoint availability check for Flyted took 0.9843149185180664s
Availability | VoID file availability check for Flyted took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Flyted took 0.3650071620941162s
Reputation | Calculation of the PageRank for Flyted took 0.021126747131347656s
Interlinking | Calculation of Degree of Connection for Flyted took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Flyted took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Flyted took 4.4345855712890625e-05s
Believability | Calculation of trust value for Flyted took 1.1920928955078125e-05s
INFO | --- Analysis for flyted took 603.5895671844482s
Availability | SPARQL endpoint availability check for Foodista took 2.568300485610962s
Availability | VoID file availability check for Foodista took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Foodista took 0.2915925979614258s
Reputation | Calculation of the PageRank for Foodista took 0.021105051040649414s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Foodista took 4.0531158447265625e-05s
Believability | Calculation of trust value for Foodista took 1.1444091796875e-05s
INFO | --- Analysis for foodista took 180.2965385913849s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17058205604553223s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.31180882453918457s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.677078247070312e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.2159347534179688e-05s
INFO | --- Analysis for foodpedia took 1.96193265914917s
Availability | SPARQL endpoint availability check for FORGE Course information took 0.041878461837768555s
Availability | VoID file availability check for FORGE Course information took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.3338491916656494s
Reputation | Calculation of the PageRank for FORGE Course information took 0.021704435348510742s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.24249267578125e-05s
Believability | Calculation of trust value for FORGE Course information took 1.811981201171875e-05s
INFO | --- Analysis for forge-course-information took 1.8673229217529297s
Availability | SPARQL endpoint availability check for FrameBase schema took 0.00010132789611816406s
Availability | VoID file availability check for FrameBase schema took 0.0008697509765625s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.3201265335083008s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02114272117614746s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.4345855712890625e-05s
Believability | Calculation of trust value for FrameBase schema took 1.2874603271484375e-05s
INFO | --- Analysis for framebase-schema took 2.476602792739868s
Availability | SPARQL endpoint availability check for FrameNet took 8.511543273925781e-05s
Availability | VoID file availability check for FrameNet took 0.000640869140625s
Completeness | Calculation of interlinking completeness for FrameNet took 0.49973630905151367s
Reputation | Calculation of the PageRank for FrameNet took 0.023354768753051758s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0009951591491699219s
Interlinking | Calculation of Clustering coefficient for FrameNet took 4.220008850097656e-05s
Believability | Calculation of trust value for FrameNet took 1.3828277587890625e-05s
INFO | --- Analysis for framenet took 3.057497262954712s
Availability | SPARQL endpoint availability check for Framester took 0.6998677253723145s
Availability | VoID file availability check for Framester took 0.0005898475646972656s
Extra | Recovery of all triples for Framester took 61.31328058242798s
Performance | Total latancy measurement for Framester took 5.23990797996521s
Amount of data | Number of triples check for Framester took 54.03362727165222s
Versatility | Languages check for Framester took 60.579153060913086s
Interpretability | Number of blank nodes check for Framester took 0.5451140403747559s
Interpretability | RDF structures check for Framester took 1.3306365013122559s
Versatility | Serialization formats check for Framester took 1.2479839324951172s
Availability | RDF dump link check for Framester took 4.799546003341675s
License | MR license check for Framester took 2.0134289264678955s
License | HR license check for Framester took 60.55450940132141s
Amount of data | Number of property check for Framester took 0.4525930881500244s
Understandability | Number of label check for Framester took 13.097746849060059s
Understandability | URI regex check for Framester took 1.3096070289611816s
Understandability | Vocabs check for Framester took 0.645113468170166s
Verifiability | Authors check for Framester took 0.6633045673370361s
Verifiability | Publishers check for Framester took 0.9416460990905762s
Performance | Throughput check for Framester took 12.778614282608032s
Amount of data | Check the number of entities for Framester took 0.00010371208190917969s
Verifiability | Contribs. check for Framester took 0.451641321182251s
Interlinking | sameAs chians check for Framester took 0.5337557792663574s
Interlinking | skos check for Framester took 1.2806768417358398s
Interlinking | skos check for Framester took 0.46341848373413086s
Timeliness | dataset update frequency check for Framester took 0.42583608627319336s
Currency | Creation date check for Framester took 0.45014071464538574s
Currency | Modification date check for Framester took 0.4598119258880615s
Rep.Conc. | URIs length for Framester took 121.03832936286926s
Interoperability | New vocabularies check for Framester took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Framester took 0.4485182762145996s
Accuracy | Check Functional Property for Framester took 0.5596487522125244s
Accuracy | Check Inverse Functional Property for Framester took 0.5368096828460693s
Consistency | Disjoint class check for Framester took 0.4596829414367676s
Consistency | Check Misplaced properties for Framester took 125.84947872161865s
Consistency | Misplaced classes for Framester took 0.6174492835998535s
Consistency | Check Ontology hijacking for Framester took 35.698162317276s
Consistency | Check Invalid usage of undefined properties for Framester took 61.889538526535034s
Conciseness | Check Extensional conciseness for Framester took 0.00014925003051757812s
Conciseness | Check Intensional conciseness for Framester took 0.6958754062652588s
Security | Sign check for Framester took 1.5700321197509766s
Completeness | Calculation of interlinking completeness for Framester took 0.3644578456878662s
Reputation | Calculation of the PageRank for Framester took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for Framester took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Framester took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Framester took 1.430511474609375e-06s
Believability | Calculation of trust value for Framester took 1.2636184692382812e-05s
INFO | --- Analysis for framester took 1101.1718957424164s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.10398626327514648s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.298492431640625s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.021167993545532227s
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.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 9.179115295410156e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for frb-linked-data took 2.5355350971221924s
Availability | SPARQL endpoint availability check for Freebase took 0.00013136863708496094s
Availability | VoID file availability check for Freebase took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for Freebase took 0.4036126136779785s
Reputation | Calculation of the PageRank for Freebase took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for Freebase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Freebase took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0002751350402832031s
Believability | Calculation of trust value for Freebase took 1.1682510375976562e-05s
INFO | --- Analysis for freebase took 4.803934574127197s
Availability | SPARQL endpoint availability check for Freeyork took 8.869171142578125e-05s
Availability | VoID file availability check for Freeyork took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Freeyork took 4.285794019699097s
Reputation | Calculation of the PageRank for Freeyork took 0.021242856979370117s
Interlinking | Calculation of Degree of Connection for Freeyork took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Freeyork took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010633468627929688s
Believability | Calculation of trust value for Freeyork took 1.1205673217773438e-05s
INFO | --- Analysis for freeyork-org took 8.305625677108765s
Availability | SPARQL endpoint availability check for French School Program took 9.298324584960938e-05s
Availability | VoID file availability check for French School Program took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for French School Program took 1.8248605728149414s
Reputation | Calculation of the PageRank for French School Program took 0.023029804229736328s
Interlinking | Calculation of Degree of Connection for French School Program took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for French School Program took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for French School Program took 2.8848648071289062e-05s
Believability | Calculation of trust value for French School Program took 1.3113021850585938e-05s
INFO | --- Analysis for french-school-program took 7.513733386993408s
Availability | SPARQL endpoint availability check for French School System took 4.315376281738281e-05s
Availability | VoID file availability check for French School System took 0.0009779930114746094s
Completeness | Calculation of interlinking completeness for French School System took 0.9011650085449219s
Reputation | Calculation of the PageRank for French School System took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for French School System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for French School System took 3.0517578125e-05s
Believability | Calculation of trust value for French School System took 1.1444091796875e-05s
INFO | --- Analysis for french-school-system took 4.831634521484375s
Availability | SPARQL endpoint availability check for French TimeBank took 8.96453857421875e-05s
Availability | VoID file availability check for French TimeBank took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.4710235595703125s
Reputation | Calculation of the PageRank for French TimeBank took 0.02180337905883789s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.075599670410156e-05s
Believability | Calculation of trust value for French TimeBank took 1.33514404296875e-05s
INFO | --- Analysis for french-timebank took 5.246690034866333s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7332861423492432s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.4488258361816406s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.022458791732788086s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.772445678710938e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-cordis took 5.223430633544922s
Availability | SPARQL endpoint availability check for DailyMed took 0.7259581089019775s
Availability | VoID file availability check for DailyMed took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for DailyMed took 0.3269357681274414s
Reputation | Calculation of the PageRank for DailyMed took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00010132789611816406s
Believability | Calculation of trust value for DailyMed took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-dailymed took 6.374263286590576s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.6971261501312256s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007696151733398438s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.7817738056182861s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020814180374145508s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.535385131835938e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-dblp took 5.208665132522583s
Availability | SPARQL endpoint availability check for Diseasome took 0.7176322937011719s
Availability | VoID file availability check for Diseasome took 0.00035858154296875s
Completeness | Calculation of interlinking completeness for Diseasome took 0.35745763778686523s
Reputation | Calculation of the PageRank for Diseasome took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for Diseasome took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Diseasome took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010824203491210938s
Believability | Calculation of trust value for Diseasome took 1.1205673217773438e-05s
INFO | --- Analysis for fu-berlin-diseasome took 6.69341516494751s
Availability | SPARQL endpoint availability check for DrugBank took 0.7063331604003906s
Availability | VoID file availability check for DrugBank took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for DrugBank took 0.32289791107177734s
Reputation | Calculation of the PageRank for DrugBank took 0.030961990356445312s
Interlinking | Calculation of Degree of Connection for DrugBank took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0022156238555908203s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00025844573974609375s
Believability | Calculation of trust value for DrugBank took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-drugbank took 6.559823751449585s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7154679298400879s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.3122391700744629s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.021992921829223633s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 2.9325485229492188e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.648006200790405s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7124366760253906s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.5426054000854492s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.021764516830444336s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0010716915130615234s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 9.202957153320312e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.996807813644409s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.717674732208252s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.3310966491699219s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02258896827697754s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0009365081787109375s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 9.322166442871094e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-eures took 4.5728068351745605s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6919906139373779s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.9398651123046875s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007836818695068359s
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.5367431640625e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.484631061553955s
Availability | SPARQL endpoint availability check for MediCare took 0.7109999656677246s
Availability | VoID file availability check for MediCare took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for MediCare took 0.4103200435638428s
Reputation | Calculation of the PageRank for MediCare took 0.02078104019165039s
Interlinking | Calculation of Degree of Connection for MediCare took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MediCare took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.172325134277344e-05s
Believability | Calculation of trust value for MediCare took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-medicare took 4.941775560379028s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7112505435943604s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.4518265724182129s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.021101713180541992s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.367134094238281e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.2636184692382812e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.774659872055054s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7092185020446777s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.45107460021972656s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.021048545837402344s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.001026153564453125s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 0.00011515617370605469s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-sider took 4.685187578201294s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.8201723098754883s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.3183767795562744s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.486343383789062e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 8.821487426757812e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.519705295562744s
Availability | SPARQL endpoint availability check for fvdb took 8.749961853027344e-05s
Availability | VoID file availability check for fvdb took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for fvdb took 0.3919355869293213s
Reputation | Calculation of the PageRank for fvdb took 0.021826744079589844s
Interlinking | Calculation of Degree of Connection for fvdb took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.3855438232421875e-05s
Believability | Calculation of trust value for fvdb took 1.2874603271484375e-05s
INFO | --- Analysis for fv took 13.234877586364746s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 0.0001316070556640625s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0008075237274169922s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.3891317844390869s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.021495342254638672s
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.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.838539123535156e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.3113021850585938e-05s
INFO | --- Analysis for GACS took 3.876234292984009s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 8.940696716308594e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0008878707885742188s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.3333284854888916s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.022791624069213867s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.337860107421875e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 1.1444091796875e-05s
INFO | --- Analysis for galen_from_co-odeorg took 237.5384063720703s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 8.940696716308594e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.3223748207092285s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.9114227294921875e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.2159347534179688e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 6.062336206436157s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 9.34600830078125e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.45572686195373535s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.022297382354736328s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.0001010894775390625s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.239776611328125e-05s
INFO | --- Analysis for garnicaplywood took 2.913344621658325s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.988380432128906e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.32250404357910156s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.021718502044677734s
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.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.441375732421875e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1205673217773438e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 10.140712976455688s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.45804691314697266s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.9881985187530518s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 1.6088786125183105s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020720481872558594s
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.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.083747863769531e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for gemet took 8.615436792373657s
Availability | SPARQL endpoint availability check for gemet-annotated took 9.059906005859375e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.31637072563171387s
Reputation | Calculation of the PageRank for gemet-annotated took 0.021207332611083984s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.457069396972656e-05s
Believability | Calculation of trust value for gemet-annotated took 1.33514404296875e-05s
INFO | --- Analysis for gemet-annotated took 7.376786231994629s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.8557078838348389s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.08591914176940918s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.7533831596374512s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.021144866943359375s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.4781951904296875e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.975781679153442s
Availability | SPARQL endpoint availability check for Super Ontology took 0.9192571640014648s
Availability | VoID file availability check for Super Ontology took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.6076829433441162s
Reputation | Calculation of the PageRank for Super Ontology took 0.021392107009887695s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0008976459503173828s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for Super Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 8.032400846481323s
Availability | SPARQL endpoint availability check for geo.place took 0.00010228157043457031s
Availability | VoID file availability check for geo.place took 0.0009586811065673828s
Completeness | Calculation of interlinking completeness for geo.place took 0.3141164779663086s
Reputation | Calculation of the PageRank for geo.place took 0.021674633026123047s
Interlinking | Calculation of Degree of Connection for geo.place took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0010404586791992188s
Interlinking | Calculation of Clustering coefficient for geo.place took 5.4836273193359375e-05s
Believability | Calculation of trust value for geo.place took 1.3113021850585938e-05s
INFO | --- Analysis for geo_place took 34.54065918922424s
Availability | SPARQL endpoint availability check for Geographic detector model took 9.107589721679688e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.5003445148468018s
Reputation | Calculation of the PageRank for Geographic detector model took 0.02270364761352539s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0012233257293701172s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.814697265625e-05s
Believability | Calculation of trust value for Geographic detector model took 1.1682510375976562e-05s
INFO | --- Analysis for GeoDetector took 19.358157634735107s
Availability | SPARQL endpoint availability check for geodomainwn took 4.458427429199219e-05s
Availability | VoID file availability check for geodomainwn took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for geodomainwn took 1.3655433654785156s
Reputation | Calculation of the PageRank for geodomainwn took 0.021343708038330078s
Interlinking | Calculation of Degree of Connection for geodomainwn took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.5299530029296875e-05s
Believability | Calculation of trust value for geodomainwn took 1.239776611328125e-05s
INFO | --- Analysis for geodomainwn took 6.423676490783691s
Availability | SPARQL endpoint availability check for GeoEcuador took 20.054380893707275s
Availability | VoID file availability check for GeoEcuador took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for GeoEcuador took 2.793987989425659s
Reputation | Calculation of the PageRank for GeoEcuador took 0.021001100540161133s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.771087646484375e-05s
Believability | Calculation of trust value for GeoEcuador took 1.2159347534179688e-05s
INFO | --- Analysis for geoecuador took 39.16797423362732s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 262.22895526885986s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007784366607666016s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.35166454315185547s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02175307273864746s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0008809566497802734s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 8.225440979003906e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.2874603271484375e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 449.44570875167847s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 0.07149934768676758s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.3374514579772949s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.025168895721435547s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0011708736419677734s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 4.363059997558594e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 1.33514404296875e-05s
INFO | --- Analysis for geographic-openuplabs took 19.792105674743652s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5118038654327393s
Availability | VoID file availability check for GeoLinkedData took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 4.192338466644287s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.021168231964111328s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0010311603546142578s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 0.00010275840759277344s
Believability | Calculation of trust value for GeoLinkedData took 9.5367431640625e-06s
INFO | --- Analysis for geolinkeddata took 20.734506130218506s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.32016873359680176s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.17371129989624023s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 9.437659978866577s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.36150407791137695s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1454160213470459s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.543607234954834s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.19532990455627441s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.18409323692321777s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.2592477798461914s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.10414862632751465s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.3378102779388428s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.061878204345703125s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.14449572563171387s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 2.2781598567962646s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.09839653968811035s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.10428261756896973s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.1459345817565918s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.08969855308532715s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.11449408531188965s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10466766357421875s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.281042098999023s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 9.417533874511719e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.09289240837097168s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.07635259628295898s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.10753726959228516s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06217455863952637s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.07499146461486816s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1008303165435791s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.10006213188171387s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.2405292987823486s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 10.40835428237915s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.09015655517578125s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07663607597351074s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.062142372131347656s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 1.871330976486206s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007721424102783203s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.23927545547485352s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.07023143768310547s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.2064063549041748s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5236763954162598s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 2.0182132720947266s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.9241938591003418s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.7609760761260986s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.18744897842407227s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.06969070434570312s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 0.9975330829620361s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.4808683395385742s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 6.001902341842651s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.5735626220703125e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 75.16231966018677s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 9.131431579589844e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.8397395610809326s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.021311283111572266s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00048422813415527344s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.33514404296875e-05s
INFO | --- Analysis for geonames-semantic-web took 3.7712478637695312s
Availability | SPARQL endpoint availability check for Geospatial World  took 9.465217590332031e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Geospatial World  took 1.7267427444458008s
Reputation | Calculation of the PageRank for Geospatial World  took 0.021961212158203125s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00012111663818359375s
Believability | Calculation of trust value for Geospatial World  took 1.2636184692382812e-05s
INFO | --- Analysis for geospatialworld-net took 5.9498291015625s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5372738838195801s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.7313022613525391s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.4403409957885742s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013446807861328125s
Interoperability | Check the re-using of existing vocabs for GeoSpecies Knowledge Base took 35.81733798980713s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.2636184692382812e-05s
INFO | --- Analysis for geospecies took 45.46000289916992s
Availability | SPARQL endpoint availability check for GeoWordNet took 0.00013017654418945312s
Availability | VoID file availability check for GeoWordNet took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for GeoWordNet took 1.0308256149291992s
Reputation | Calculation of the PageRank for GeoWordNet took 0.021937131881713867s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.9604644775390625e-05s
Believability | Calculation of trust value for GeoWordNet took 1.2874603271484375e-05s
INFO | --- Analysis for geowordnet took 19.22218155860901s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.08551764488220215s
Availability | VoID file availability check for German labor law thesaurus took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.3198263645172119s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.021488428115844727s
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.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 9.012222290039062e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 10.073235034942627s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 8.893013000488281e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.8105747699737549s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.021752357482910156s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.649162292480469e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.2159347534179688e-05s
INFO | --- Analysis for germlex took 5.182444095611572s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.8909158706665039s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.30838537216186523s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.845329284667969e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1920928955078125e-05s
INFO | --- Analysis for gesis-thesoz took 7.727543354034424s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 1.7206623554229736s
Availability | VoID file availability check for Art & Architecture Thesaurus took 2.5463309288024902s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.32557082176208496s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.022817373275756836s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.867813110351562e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for getty-aat took 15.255738258361816s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.3152484893798828s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.3028140068054199s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.022814273834228516s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0010509490966796875s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 6.341934204101562e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.2874603271484375e-05s
INFO | --- Analysis for getty-tgn took 12.19715690612793s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 262.74885153770447s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 1.1439051628112793s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.024606704711914062s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 5.888938903808594e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 9.059906005859375e-06s
INFO | --- Analysis for gipuzkoademografia took 438.0077941417694s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 8.487701416015625e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.461869478225708s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0008187294006347656s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.266334533691406e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 8.821487426757812e-06s
INFO | --- Analysis for glastonbury-2011 took 5.378985404968262s
Availability | SPARQL endpoint availability check for Global Change Information System took 0.35562610626220703s
Availability | VoID file availability check for Global Change Information System took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Global Change Information System took 1.9575073719024658s
Reputation | Calculation of the PageRank for Global Change Information System took 0.0212247371673584s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.337860107421875e-05s
Believability | Calculation of trust value for Global Change Information System took 3.838539123535156e-05s
INFO | --- Analysis for global-change-information-system took 6.787903070449829s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 9.036064147949219e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.3050272464752197s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.021083354949951172s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.2928924560546875e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 8.58306884765625e-06s
INFO | --- Analysis for global-hunger-index-2011 took 4.8438379764556885s
Availability | SPARQL endpoint availability check for Glottolog took 4.553794860839844e-05s
Availability | VoID file availability check for Glottolog took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Glottolog took 2.064521312713623s
Reputation | Calculation of the PageRank for Glottolog took 0.022287845611572266s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.001077890396118164s
Interlinking | Calculation of Clustering coefficient for Glottolog took 6.937980651855469e-05s
Believability | Calculation of trust value for Glottolog took 1.33514404296875e-05s
INFO | --- Analysis for glottolog took 11.577558040618896s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 8.630752563476562e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.6145615577697754s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 1.1378753185272217s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.021974802017211914s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0008420944213867188s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00013399124145507812s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.1444091796875e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 21.23742651939392s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 5.6743621826171875e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.3960137367248535s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.023444652557373047s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 3.266334533691406e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 1.0967254638671875e-05s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 13.63961148262024s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 9.608268737792969e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0008347034454345703s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.4563109874725342s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.021016836166381836s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.315376281738281e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.4781951904296875e-05s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 118.08782625198364s
Availability | SPARQL endpoint availability check for 1121 took 9.274482727050781e-05s
Availability | VoID file availability check for 1121 took 0.0004010200500488281s
Completeness | Calculation of interlinking completeness for 1121 took 39.21849346160889s
Reputation | Calculation of the PageRank for 1121 took 0.021375179290771484s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for 1121 took 4.267692565917969e-05s
Believability | Calculation of trust value for 1121 took 7.3909759521484375e-06s
INFO | --- Analysis for God_ took 193.26681113243103s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 8.96453857421875e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 40.928685903549194s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.021384477615356445s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.340576171875e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.1920928955078125e-05s
INFO | --- Analysis for gold took 168.0048885345459s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 0.00010514259338378906s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 41.68995523452759s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.021509647369384766s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.985664367675781e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.239776611328125e-05s
INFO | --- Analysis for googleart-wrapper took 185.0561978816986s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.09785103797912598s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.31595444679260254s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.021511316299438477s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.57763671875e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.1920928955078125e-05s
INFO | --- Analysis for govagribus-denmark took 216.57431364059448s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 0.7146594524383545s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 59.49015402793884s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 9.894371032714844e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for government-web-integration-for-linked-data took 242.83215355873108s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.698791742324829s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 180.29309344291687s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.02131962776184082s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 0.00010180473327636719s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 9.775161743164062e-06s
INFO | --- Analysis for govtrack took 486.55276823043823s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 0.00010037422180175781s
Availability | VoID file availability check for greek-administrative-geography took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.3176882266998291s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02192091941833496s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 7.224082946777344e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.1682510375976562e-05s
INFO | --- Analysis for greek-administrative-geography took 104.60062766075134s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.17226815223693848s
Availability | VoID file availability check for Greek Wordnet took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 6.565390586853027s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.021000385284423828s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.649162292480469e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.1444091796875e-05s
INFO | --- Analysis for greek-wordnet took 25.3876793384552s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.8099086284637451s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0003490447998046875s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.5218889713287354s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021093368530273438s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.082389831542969e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.1920928955078125e-05s
INFO | --- Analysis for greekchildrensartmuseum took 4.294131278991699s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 0.00017905235290527344s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.8601863384246826s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2942080497741699s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020975351333618164s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010514259338378906s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 6.687688827514648s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.641880989074707s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.30429673194885254s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.02687692642211914s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0014030933380126953s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 7.653236389160156e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.1920928955078125e-05s
INFO | --- Analysis for grrp took 4.073112964630127s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.5325031280517578s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.33179283142089844s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.532669067382812e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 7.62939453125e-06s
INFO | --- Analysis for grrt took 3.277477502822876s
Availability | SPARQL endpoint availability check for Geological Timescale took 0.7225558757781982s
Availability | VoID file availability check for Geological Timescale took 0.00047779083251953125s
Extra | Recovery of all triples for Geological Timescale took 7.14335560798645s
Performance | Total latancy measurement for Geological Timescale took 3.0410983562469482s
Amount of data | Number of triples check for Geological Timescale took 0.6861252784729004s
Interoperability | New terms check for Geological Timescale took 2.0740463733673096s
Versatility | Languages check for Geological Timescale took 0.8049609661102295s
Interpretability | Number of blank nodes check for Geological Timescale took 0.6855359077453613s
Security | Check HTTPS for Geological Timescale took 1.2212073802947998s
Interpretability | RDF structures check for Geological Timescale took 0.6629071235656738s
Versatility | Serialization formats check for Geological Timescale took 0.6287441253662109s
Availability | RDF dump link check for Geological Timescale took 1.3425273895263672s
License | MR license check for Geological Timescale took 0.6840114593505859s
License | HR license check for Geological Timescale took 0.6515755653381348s
Amount of data | Number of property check for Geological Timescale took 0.6301512718200684s
Understandability | Number of label check for Geological Timescale took 0.6703190803527832s
Understandability | URI regex check for Geological Timescale took 1.2525651454925537s
Understandability | Vocabs check for Geological Timescale took 0.6342551708221436s
Verifiability | Authors check for Geological Timescale took 0.6365017890930176s
Verifiability | Publishers check for Geological Timescale took 0.608635663986206s
Performance | Throughput check for Geological Timescale took 12.208430051803589s
Amount of data | Check the number of entities for Geological Timescale took 0.02319049835205078s
Verifiability | Contribs. check for Geological Timescale took 0.635451078414917s
Interlinking | sameAs chians check for Geological Timescale took 0.6365337371826172s
Interlinking | skos check for Geological Timescale took 0.6066558361053467s
Interlinking | skos check for Geological Timescale took 0.6048243045806885s
Timeliness | dataset update frequency check for Geological Timescale took 0.6147451400756836s
Currency | Creation date check for Geological Timescale took 0.6365211009979248s
Currency | Modification date check for Geological Timescale took 0.6281046867370605s
Rep.Conc. | URIs length for Geological Timescale took 3.2057433128356934s
Interoperability | New vocabularies check for Geological Timescale took 29.422895431518555s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.6366748809814453s
Accuracy | Check Functional Property for Geological Timescale took 0.6283836364746094s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.6076996326446533s
Accuracy | Check Empty annotation labels for Geological Timescale took 2.4828202724456787s
Accuracy | Check White space in annotation for Geological Timescale took 0.016420364379882812s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07860708236694336s
Consistency | Disjoint class check for Geological Timescale took 0.6077415943145752s
Consistency | Check Misplaced properties for Geological Timescale took 1.2549042701721191s
Consistency | Misplaced classes for Geological Timescale took 0.7967395782470703s
Consistency | Check Ontology hijacking for Geological Timescale took 3.276421546936035s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.4114964008331299s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.0740859508514404s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05703091621398926s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.9491496086120605s
Security | Sign check for Geological Timescale took 0.6189920902252197s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.2288928031921387s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.3587203025817871s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02276897430419922s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0009882450103759766s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 10.423813819885254s
Believability | Calculation of trust value for Geological Timescale took 1.33514404296875e-05s
INFO | --- Analysis for GTS took 144.60095834732056s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.8582522869110107s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for GTS-ont took 7.960813283920288s
Availability | SPARQL endpoint availability check for GUTSTOK  took 9.393692016601562e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 2.429286241531372s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02121114730834961s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.9087066650390625e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.2159347534179688e-05s
INFO | --- Analysis for Guillaume_Forget took 7.72196626663208s
Availability | SPARQL endpoint availability check for Project Gutenberg took 0.00011086463928222656s
Availability | VoID file availability check for Project Gutenberg took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.40806126594543457s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02183699607849121s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.009506225585938e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.1682510375976562e-05s
INFO | --- Analysis for gutenberg took 7.908606290817261s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 8.940696716308594e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.9048125743865967s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020735502243041992s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.5762786865234375e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.2636184692382812e-05s
INFO | --- Analysis for gwa-ili took 7.243351459503174s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 0.00010752677917480469s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.3380141258239746s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02209949493408203s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0010867118835449219s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.719329833984375e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.1444091796875e-05s
INFO | --- Analysis for GWR took 20.46372675895691s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.5299530029296875e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.3380711078643799s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.021704435348510742s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.170967102050781e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.1444091796875e-05s
INFO | --- Analysis for HASM took 20.431722164154053s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 30.538793802261353s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.3045461177825928s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.02097153663635254s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 2.8848648071289062e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 1.0251998901367188e-05s
INFO | --- Analysis for hcls-knowledge-base took 44.0615291595459s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 7.099680185317993s
Availability | VoID file availability check for HealthCare Ontology took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.45395755767822266s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02113962173461914s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for HealthCare_Ontology took 13.643110275268555s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 9.131431579589844e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.34058165550231934s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.0211484432220459s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.008148193359375e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.239776611328125e-05s
INFO | --- Analysis for heartfailure took 2.5772573947906494s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.677013635635376s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0010917186737060547s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.3712272644042969s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020808696746826172s
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.5497207641601562e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.76837158203125e-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.1444091796875e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 101.23929643630981s
Availability | SPARQL endpoint availability check for Hedatuz took 0.24667048454284668s
Availability | VoID file availability check for Hedatuz took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.6142218112945557s
Reputation | Calculation of the PageRank for Hedatuz took 0.023194551467895508s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.124641418457031e-05s
Believability | Calculation of trust value for Hedatuz took 1.3589859008789062e-05s
INFO | --- Analysis for hedatuz took 4.531392574310303s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.15615439414978027s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 1.374222755432129s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02126288414001465s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012683868408203125s
Believability | Calculation of trust value for Hellenic Fire Brigade took 9.775161743164062e-06s
INFO | --- Analysis for hellenic-fire-brigade took 4.547078371047974s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.01858377456665039s
Availability | VoID file availability check for Hellenic Police took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.3187408447265625s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02099776268005371s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001316070556640625s
Believability | Calculation of trust value for Hellenic Police took 1.2874603271484375e-05s
INFO | --- Analysis for hellenic-police took 2.892054796218872s
Availability | SPARQL endpoint availability check for Hermos took 8.487701416015625e-05s
Availability | VoID file availability check for Hermos took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Hermos took 0.6052579879760742s
Reputation | Calculation of the PageRank for Hermos took 0.02305126190185547s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.8848648071289062e-05s
Believability | Calculation of trust value for Hermos took 1.049041748046875e-05s
INFO | --- Analysis for Hermos took 3.494978427886963s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 8.821487426757812e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.32208800315856934s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.021091938018798828s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.8848648071289062e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.1682510375976562e-05s
INFO | --- Analysis for Himanshu_Mahawar took 3.216193199157715s
Availability | SPARQL endpoint availability check for HITO took 0.444382905960083s
Availability | VoID file availability check for HITO took 0.0007307529449462891s
Extra | Recovery of all triples for HITO took 1.72869873046875s
Performance | Total latancy measurement for HITO took 1.0005550384521484s
Amount of data | Number of triples check for HITO took 0.2168445587158203s
Interoperability | New terms check for HITO took 1.600602388381958s
Versatility | Languages check for HITO took 0.22729992866516113s
Interpretability | Number of blank nodes check for HITO took 0.19874787330627441s
Interpretability | RDF structures check for HITO took 0.2287294864654541s
Versatility | Serialization formats check for HITO took 0.21020889282226562s
Availability | RDF dump link check for HITO took 0.19694066047668457s
License | MR license check for HITO took 0.19892621040344238s
License | HR license check for HITO took 0.22102570533752441s
Amount of data | Number of property check for HITO took 0.2025129795074463s
Understandability | Number of label check for HITO took 0.22836875915527344s
Understandability | URI regex check for HITO took 0.3861074447631836s
Understandability | Vocabs check for HITO took 0.1860640048980713s
Verifiability | Authors check for HITO took 0.20219922065734863s
Verifiability | Publishers check for HITO took 0.21167349815368652s
Performance | Throughput check for HITO took 11.692819356918335s
Amount of data | Check the number of entities for HITO took 9.226799011230469e-05s
Verifiability | Contribs. check for HITO took 0.19030141830444336s
Interlinking | sameAs chians check for HITO took 0.1973426342010498s
Interlinking | skos check for HITO took 0.20435047149658203s
Interlinking | skos check for HITO took 0.18625879287719727s
Timeliness | dataset update frequency check for HITO took 0.21044635772705078s
Currency | Creation date check for HITO took 0.2174532413482666s
Currency | Modification date check for HITO took 0.19250917434692383s
Rep.Conc. | URIs length for HITO took 1.0445692539215088s
Interoperability | New vocabularies check for HITO took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.20732951164245605s
Accuracy | Check Functional Property for HITO took 0.1985938549041748s
Accuracy | Check Inverse Functional Property for HITO took 0.18723797798156738s
Accuracy | Check Empty annotation labels for HITO took 0.5254106521606445s
Accuracy | Check White space in annotation for HITO took 0.01366734504699707s
Accuracy | Check Datatype consistency for HITO took 0.07804155349731445s
Consistency | Disjoint class check for HITO took 0.1969466209411621s
Consistency | Check Misplaced properties for HITO took 0.5209424495697021s
Consistency | Misplaced classes for HITO took 0.3734011650085449s
Consistency | Check Ontology hijacking for HITO took 1.8284492492675781s
Consistency | Check Invalid usage of undefined classes for HITO took 1.3666284084320068s
Consistency | Check Invalid usage of undefined properties for HITO took 1.6360690593719482s
Conciseness | Check Extensional conciseness for HITO took 0.06755566596984863s
Conciseness | Check Intensional conciseness for HITO took 0.19805479049682617s
Security | Sign check for HITO took 0.19133424758911133s
Availability | Check URIs Dereferenciability for HITO took 2162.1654086112976s
Completeness | Calculation of interlinking completeness for HITO took 36.986032009124756s
Reputation | Calculation of the PageRank for HITO took 0.0283663272857666s
Interlinking | Calculation of Degree of Connection for HITO took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for HITO took 9.417533874511719e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.6689300537109375e-06s
Believability | Calculation of trust value for HITO took 1.4066696166992188e-05s
INFO | --- Analysis for hito took 2337.504060983658s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 16.031605005264282s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 46.54843807220459s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02203202247619629s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.001032114028930664s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 5.5789947509765625e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.1205673217773438e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 202.31526446342468s
Availability | SPARQL endpoint availability check for Homologene took 5.269050598144531e-05s
Availability | VoID file availability check for Homologene took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for Homologene took 0.298677921295166s
Reputation | Calculation of the PageRank for Homologene took 0.02184319496154785s
Interlinking | Calculation of Degree of Connection for Homologene took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Homologene took 4.0531158447265625e-05s
Believability | Calculation of trust value for Homologene took 1.239776611328125e-05s
INFO | --- Analysis for homologene took 155.34309148788452s
Availability | SPARQL endpoint availability check for gseg took 0.00013685226440429688s
Availability | VoID file availability check for gseg took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for gseg took 119.56333184242249s
Reputation | Calculation of the PageRank for gseg took 0.021639108657836914s
Interlinking | Calculation of Degree of Connection for gseg took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for gseg took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for gseg took 4.363059997558594e-05s
Believability | Calculation of trust value for gseg took 1.1205673217773438e-05s
INFO | --- Analysis for hongse took 240.51900815963745s
Availability | SPARQL endpoint availability check for Noticias Universia took 6.008148193359375e-05s
Availability | VoID file availability check for Noticias Universia took 0.0003266334533691406s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.2972712516784668s
Reputation | Calculation of the PageRank for Noticias Universia took 0.0217282772064209s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 2.6464462280273438e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.001132965087890625s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 5.745887756347656e-05s
Believability | Calculation of trust value for Noticias Universia took 8.106231689453125e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 479.6531183719635s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 8.988380432128906e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.3001370429992676s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.021547794342041016s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 2.9325485229492188e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.1444091796875e-05s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 13.046713590621948s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.500662088394165s
Availability | VoID file availability check for COURAGE Dataset took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.31127309799194336s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.022287845611572266s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0011785030364990234s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 4.118807554244995s
Availability | SPARQL endpoint availability check for RoadTrb took 9.059906005859375e-05s
Availability | VoID file availability check for RoadTrb took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.375990629196167s
Reputation | Calculation of the PageRank for RoadTrb took 0.021649599075317383s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.0040740966796875e-05s
Believability | Calculation of trust value for RoadTrb took 1.0728836059570312e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.418367385864258s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 9.393692016601562e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0008020401000976562s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.3612027168273926s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.790855407714844e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.1444091796875e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 28.5928692817688s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 9.822845458984375e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.35499024391174316s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.02140641212463379s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.9802322387695312e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.1444091796875e-05s
INFO | --- Analysis for http:pakistan.com took 2.428513526916504s
Availability | SPARQL endpoint availability check for CEDICT took 9.202957153320312e-05s
Availability | VoID file availability check for CEDICT took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for CEDICT took 0.33595967292785645s
Reputation | Calculation of the PageRank for CEDICT took 0.02129817008972168s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.170967102050781e-05s
Believability | Calculation of trust value for CEDICT took 1.1682510375976562e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.572687387466431s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.8963775634765625s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.8889214992523193s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.022345781326293945s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0010399818420410156s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.083747863769531e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2159347534179688e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.854482412338257s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 8.416175842285156e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.43980884552001953s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.021074533462524414s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 7.867813110351562e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.1179049015045166s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 9.918212890625e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.3254718780517578s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.02104473114013672s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.0279159545898438e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.3113021850585938e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 1.8310120105743408s
Availability | SPARQL endpoint availability check for Soccer Dataset took 9.131431579589844e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.31389403343200684s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.021976470947265625s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for http:www.msm.com took 1.8503990173339844s
Availability | SPARQL endpoint availability check for Game Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Game Ontology took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.3265721797943115s
Reputation | Calculation of the PageRank for Game Ontology took 0.022264957427978516s
Interlinking | Calculation of Degree of Connection for Game Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 2.8133392333984375e-05s
Believability | Calculation of trust value for Game Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.2731754779815674s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.988380432128906e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.3573153018951416s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0967254638671875e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 2.674023389816284s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.988380432128906e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.3451700210571289s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02145075798034668s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007479190826416016s
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.049041748046875e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 1.958481788635254s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.560585021972656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.36353135108947754s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02153158187866211s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0008671283721923828s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.504753112792969e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1682510375976562e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.1207544803619385s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.036064147949219e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.49932360649108887s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02191615104675293s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.075599670410156e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0251998901367188e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.1616053581237793s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.792213439941406e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3581376075744629s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021080732345581055s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8848648071289062e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1682510375976562e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 1.9167697429656982s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.036064147949219e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3477137088775635s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020953893661499023s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1920928955078125e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.4450953006744385s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.821487426757812e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.34583401679992676s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0994415283203125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1920928955078125e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.126689910888672s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0001010894775390625s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.32376718521118164s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.02210688591003418s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.8133392333984375e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0728836059570312e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 10.50691819190979s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.1415414810180664s
Availability | VoID file availability check for Bookkeeping took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.32805871963500977s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020984888076782227s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.743171691894531e-05s
Believability | Calculation of trust value for Bookkeeping took 1.1205673217773438e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 3.4263839721679688s
Availability | SPARQL endpoint availability check for Legal Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Legal Ontology took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.33114075660705566s
Reputation | Calculation of the PageRank for Legal Ontology took 0.021258831024169922s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.838539123535156e-05s
Believability | Calculation of trust value for Legal Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.0995383262634277s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 8.893013000488281e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.31278133392333984s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02245020866394043s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.225440979003906e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.33514404296875e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.3414738178253174s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 7.390975952148438e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.34382033348083496s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.026099681854248047s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0016021728515625s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 4.792213439941406e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 7.152557373046875e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.1450634002685547s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 8.726119995117188e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0007548332214355469s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.31486034393310547s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.02116084098815918s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.123283386230469e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 1.2159347534179688e-05s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 7.808300495147705s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 1.0054113864898682s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.3102107048034668s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.02196979522705078s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.552436828613281e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 1.2159347534179688e-05s
INFO | --- Analysis for hud-library-usagedata took 3.5503034591674805s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.41486549377441406s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.3237004280090332s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.022431373596191406s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010704994201660156s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.430511474609375e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 4.581154108047485s
Availability | SPARQL endpoint availability check for IATE RDF took 6.556510925292969e-05s
Availability | VoID file availability check for IATE RDF took 0.0012669563293457031s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.319934606552124s
Reputation | Calculation of the PageRank for IATE RDF took 0.021127939224243164s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for IATE RDF took 1.1920928955078125e-05s
INFO | --- Analysis for iate-rdf took 4.810935735702515s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.28640341758728s
Availability | VoID file availability check for IATI as Linked Data took 0.0007557868957519531s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2916412353515625s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0008449554443359375s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 9.846687316894531e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for iati-as-linked-data took 12.998795509338379s
Availability | SPARQL endpoint availability check for ICANE took 3.5520527362823486s
Availability | VoID file availability check for ICANE took 0.0004134178161621094s
Completeness | Calculation of interlinking completeness for ICANE took 0.32884645462036133s
Reputation | Calculation of the PageRank for ICANE took 0.024279356002807617s
Interlinking | Calculation of Degree of Connection for ICANE took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0014643669128417969s
Interlinking | Calculation of Clustering coefficient for ICANE took 0.00013256072998046875s
Believability | Calculation of trust value for ICANE took 1.0251998901367188e-05s
INFO | --- Analysis for icane took 8.525999784469604s
Availability | SPARQL endpoint availability check for ichoose took 0.16173052787780762s
Availability | VoID file availability check for ichoose took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for ichoose took 2.4713492393493652s
Reputation | Calculation of the PageRank for ichoose took 0.021314144134521484s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.748603820800781e-05s
Believability | Calculation of trust value for ichoose took 1.239776611328125e-05s
INFO | --- Analysis for ichoose took 71.6832685470581s
Availability | SPARQL endpoint availability check for Identifiers.org took 0.2904787063598633s
Availability | VoID file availability check for Identifiers.org took 0.19489359855651855s
Completeness | Calculation of interlinking completeness for Identifiers.org took 1.2314889430999756s
Reputation | Calculation of the PageRank for Identifiers.org took 0.0211789608001709s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.981590270996094e-05s
Believability | Calculation of trust value for Identifiers.org took 1.239776611328125e-05s
INFO | --- Analysis for identifiers-org took 5.274681329727173s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.482269287109375e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.30452513694763184s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02432990074157715s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0010333061218261719s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 9.465217590332031e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.239776611328125e-05s
INFO | --- Analysis for idreffr took 4.5659568309783936s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 40.67718148231506s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0009198188781738281s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 1.037142276763916s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.021175622940063477s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 6.175041198730469e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.1920928955078125e-05s
INFO | --- Analysis for ids took 105.88232684135437s
Availability | SPARQL endpoint availability check for ietflang took 9.059906005859375e-05s
Availability | VoID file availability check for ietflang took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for ietflang took 1.6232805252075195s
Reputation | Calculation of the PageRank for ietflang took 0.02375340461730957s
Interlinking | Calculation of Degree of Connection for ietflang took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0011909008026123047s
Interlinking | Calculation of Clustering coefficient for ietflang took 6.127357482910156e-05s
Believability | Calculation of trust value for ietflang took 1.239776611328125e-05s
INFO | --- Analysis for ietflang took 13.479596853256226s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6221237182617188s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.840216875076294s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.023740530014038086s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0013492107391357422s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 5.698204040527344e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.3589859008789062e-05s
INFO | --- Analysis for IGVLL took 6.929056882858276s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.43271446228027344s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0006358623504638672s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.295921802520752s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9859542846679688s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.19830608367919922s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.6072008609771729s
Versatility | Languages check for 3LGM² IHE Ontology took 0.20570921897888184s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.20899462699890137s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.2194678783416748s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.18956708908081055s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.1987159252166748s
License | MR license check for 3LGM² IHE Ontology took 0.20844149589538574s
License | HR license check for 3LGM² IHE Ontology took 0.23122572898864746s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.21286511421203613s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.21369647979736328s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.4081306457519531s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.20883917808532715s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.20147275924682617s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.21010112762451172s
Performance | Throughput check for 3LGM² IHE Ontology took 11.623887062072754s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 9.036064147949219e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.2089698314666748s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.19722509384155273s
Interlinking | skos check for 3LGM² IHE Ontology took 0.2040998935699463s
Interlinking | skos check for 3LGM² IHE Ontology took 0.18639349937438965s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.21588349342346191s
Currency | Creation date check for 3LGM² IHE Ontology took 0.1945054531097412s
Currency | Modification date check for 3LGM² IHE Ontology took 0.2018730640411377s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.7958016395568848s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.20819687843322754s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.20888900756835938s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.20886850357055664s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.33507704734802246s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.001886606216430664s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05186033248901367s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.197035551071167s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.46329712867736816s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2725532054901123s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.7209932804107666s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.410480260848999s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.637162446975708s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03215646743774414s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.19940805435180664s
Security | Sign check for 3LGM² IHE Ontology took 0.2072465419769287s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 502.19242906570435s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 1.4336133003234863s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.021310806274414062s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.933906555175781e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.9073486328125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for IHE took 550.8574016094208s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.6147966384887695s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0007154941558837891s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 5.739090919494629s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 7.757211685180664s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 18.463110208511353s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.1288583278656s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.54896640777588s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.7329754829406738s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.0252423286437988s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.9768574237823486s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.570556879043579s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.5797483921051025s
License | MR license check for Test Site, LOD Lab 317 took 1.7219250202178955s
License | HR license check for Test Site, LOD Lab 317 took 1.9293794631958008s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.6464617252349854s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.824937105178833s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.2035880088806152s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.5841236114501953s
Verifiability | Authors check for Test Site, LOD Lab 317 took 3.4312546253204346s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 2.8175370693206787s
Performance | Throughput check for Test Site, LOD Lab 317 took 15.656963109970093s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 8.702278137207031e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.5560493469238281s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.568565845489502s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.6837060451507568s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.5842792987823486s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.6367413997650146s
Currency | Creation date check for Test Site, LOD Lab 317 took 1.6178901195526123s
Currency | Modification date check for Test Site, LOD Lab 317 took 1.581500768661499s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 29.592684268951416s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.564284324645996s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.5661394596099854s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.6012616157531738s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.5422863960266113s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 25.623164892196655s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 1.8177340030670166s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 2.6369478702545166s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 24.34321904182434s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.0001590251922607422s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.2136294841766357s
Security | Sign check for Test Site, LOD Lab 317 took 1.6690318584442139s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.38301563262939453s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021142005920410156s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.3828277587890625e-05s
INFO | --- Analysis for iislod-test took 500.1610150337219s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 0.00010251998901367188s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 1.1913039684295654s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 2.8133392333984375e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.1920928955078125e-05s
INFO | --- Analysis for ILUSOC took 20.852946996688843s
Availability | SPARQL endpoint availability check for im@sparql took 6.158512115478516s
Availability | VoID file availability check for im@sparql took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for im@sparql took 0.6984572410583496s
Reputation | Calculation of the PageRank for im@sparql took 0.03412628173828125s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0013332366943359375s
Interlinking | Calculation of Clustering coefficient for im@sparql took 4.4345855712890625e-05s
Believability | Calculation of trust value for im@sparql took 1.1444091796875e-05s
INFO | --- Analysis for im@sparql took 12.121901512145996s
Availability | SPARQL endpoint availability check for imagery bailingniao took 0.00010085105895996094s
Availability | VoID file availability check for imagery bailingniao took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 1.6560695171356201s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.022730350494384766s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.218650817871094e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.2159347534179688e-05s
INFO | --- Analysis for imagery_bailingniao took 7.285997629165649s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1207520961761475s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.6705360412597656s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 21.512874841690063s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.453925848007202s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.844348907470703s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.365023612976074s
Versatility | Languages check for Imagesnippets Image Descriptions took 19.92506766319275s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.592729568481445s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7092876434326172s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7437803745269775s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7406723499298096s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7398080825805664s
License | MR license check for Imagesnippets Image Descriptions took 0.8570177555084229s
License | HR license check for Imagesnippets Image Descriptions took 30.72536015510559s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7433831691741943s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.6558027267456055s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.423586130142212s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7060747146606445s
Verifiability | Authors check for Imagesnippets Image Descriptions took 1.6607651710510254s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7157948017120361s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.950427532196045s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 9.322166442871094e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7390844821929932s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.695561408996582s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7488651275634766s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6985552310943604s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.729985237121582s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.4460127353668213s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4722306728363037s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.5773606300354s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7432363033294678s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7482767105102539s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7244524955749512s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 12.003111839294434s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2764389514923096s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.3966593742370605s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7279489040374756s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 8.099737167358398s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 4.967013835906982s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.4110276699066162s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 9.005155563354492s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 3.0659334659576416s
Security | Sign check for Imagesnippets Image Descriptions took 0.7421460151672363s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 12.873830318450928s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.7121579647064209s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.021168947219848633s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 2.1457672119140625e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.3828277587890625e-05s
INFO | --- Analysis for imagesnippets took 381.3859565258026s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.2317655086517334s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 1.6498103141784668s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.023287057876586914s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0011434555053710938s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 0.00012731552124023438s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for imf-linked-data took 6.538054943084717s
Availability | SPARQL endpoint availability check for IMGpedia took 1.9784908294677734s
Availability | VoID file availability check for IMGpedia took 0.0006284713745117188s
Extra | Recovery of all triples for IMGpedia took 73.69408512115479s
Performance | Total latancy measurement for IMGpedia took 5.442568063735962s
Amount of data | Number of triples check for IMGpedia took 126.21408295631409s
Interoperability | New terms check for IMGpedia took 148.30136394500732s
Versatility | Languages check for IMGpedia took 300.99101305007935s
Interpretability | Number of blank nodes check for IMGpedia took 1.1368188858032227s
Security | Check HTTPS for IMGpedia took 0.6647961139678955s
Interpretability | RDF structures check for IMGpedia took 1.1030900478363037s
Versatility | Serialization formats check for IMGpedia took 1.1003539562225342s
Availability | RDF dump link check for IMGpedia took 1.108808994293213s
License | MR license check for IMGpedia took 1.1853153705596924s
License | HR license check for IMGpedia took 300.9102132320404s
Amount of data | Number of property check for IMGpedia took 1.1201117038726807s
Understandability | Number of label check for IMGpedia took 71.6514003276825s
Understandability | URI regex check for IMGpedia took 2.3468339443206787s
Understandability | Vocabs check for IMGpedia took 1.1059021949768066s
Verifiability | Authors check for IMGpedia took 1.123448371887207s
Verifiability | Publishers check for IMGpedia took 1.1167285442352295s
Performance | Throughput check for IMGpedia took 10.859992980957031s
Amount of data | Check the number of entities for IMGpedia took 8.702278137207031e-05s
Verifiability | Contribs. check for IMGpedia took 1.1236369609832764s
Interlinking | sameAs chians check for IMGpedia took 1.6637599468231201s
Interlinking | skos check for IMGpedia took 1.1054706573486328s
Interlinking | skos check for IMGpedia took 1.0792734622955322s
Timeliness | dataset update frequency check for IMGpedia took 1.1238229274749756s
Currency | Creation date check for IMGpedia took 1.1077594757080078s
Currency | Modification date check for IMGpedia took 1.1081483364105225s
Rep.Conc. | URIs length for IMGpedia took 491.2332093715668s
Interoperability | New vocabularies check for IMGpedia took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for IMGpedia took 1.1029672622680664s
Accuracy | Check Functional Property for IMGpedia took 1.0962486267089844s
Accuracy | Check Inverse Functional Property for IMGpedia took 1.1218664646148682s
Accuracy | Check Empty annotation labels for IMGpedia took 44.54977560043335s
Accuracy | Check White space in annotation for IMGpedia took 2.5531251430511475s
Consistency | Disjoint class check for IMGpedia took 1.2196381092071533s
Consistency | Check Misplaced properties for IMGpedia took 303.2293004989624s
Consistency | Misplaced classes for IMGpedia took 3.1636807918548584s
Consistency | Check Ontology hijacking for IMGpedia took 28.15303921699524s
Consistency | Check Invalid usage of undefined properties for IMGpedia took 302.2988781929016s
Conciseness | Check Extensional conciseness for IMGpedia took 0.000217437744140625s
Conciseness | Check Intensional conciseness for IMGpedia took 4.407839298248291s
Security | Sign check for IMGpedia took 1.106736660003662s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.7294087409973145s
Reputation | Calculation of the PageRank for IMGpedia took 0.021935701370239258s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for IMGpedia took 1.9073486328125e-06s
Believability | Calculation of trust value for IMGpedia took 1.3113021850585938e-05s
INFO | --- Analysis for imgpedia took 3143.6502776145935s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 8.702278137207031e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 1.0687651634216309s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.026077985763549805s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0013082027435302734s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 6.866455078125e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 1.2159347534179688e-05s
INFO | --- Analysis for import-status-of-gmo-crops took 59.46430039405823s
Availability | SPARQL endpoint availability check for Royalty Free Music took 9.059906005859375e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.4432945251464844s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.022552490234375s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0010302066802978516s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 4.1484832763671875e-05s
Believability | Calculation of trust value for Royalty Free Music took 1.1444091796875e-05s
INFO | --- Analysis for inaudio.org took 42.46941947937012s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 8.916854858398438e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 13.78000283241272s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.02135014533996582s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.528594970703125e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 0.0001327991485595703s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 84.01813554763794s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 9.989738464355469e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.3187265396118164s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.021421432495117188s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.147125244140625e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 1.1920928955078125e-05s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 34.55546689033508s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.5945394039154053s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 1.6148788928985596s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.021063804626464844s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 51.71594452857971s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 6.3361451625823975s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.219257116317749s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.02348184585571289s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.910064697265625e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.2159347534179688e-05s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 25.593859910964966s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 7.367134094238281e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.315720796585083s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.022233247756958008s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0010523796081542969s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00012731552124023438s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.2159347534179688e-05s
INFO | --- Analysis for ineverycrea took 22.014050722122192s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.560585021972656e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.5244629383087158s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.021574020385742188s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0008726119995117188s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0001285076141357422s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.106231689453125e-06s
INFO | --- Analysis for ineverycrea-argentina took 11.35205602645874s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 272.45700788497925s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 30.939039945602417s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.021839141845703125s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0009462833404541016s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 0.00010728836059570312s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.239776611328125e-05s
INFO | --- Analysis for influence-tracker-dataset took 558.2547614574432s
Availability | SPARQL endpoint availability check for INSEMTIVES took 0.7284989356994629s
Availability | VoID file availability check for INSEMTIVES took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 37.21746063232422s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.022040128707885742s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 5.841255187988281e-05s
Believability | Calculation of trust value for INSEMTIVES took 3.314018249511719e-05s
INFO | --- Analysis for insemtives took 182.8247561454773s
Availability | SPARQL endpoint availability check for instagram.person took 9.1552734375e-05s
Availability | VoID file availability check for instagram.person took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for instagram.person took 17.136468172073364s
Reputation | Calculation of the PageRank for instagram.person took 0.022588491439819336s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0010788440704345703s
Interlinking | Calculation of Clustering coefficient for instagram.person took 6.866455078125e-05s
Believability | Calculation of trust value for instagram.person took 1.1920928955078125e-05s
INFO | --- Analysis for instagram_person took 195.74114227294922s
Availability | SPARQL endpoint availability check for instagram.videoobject took 8.988380432128906e-05s
Availability | VoID file availability check for instagram.videoobject took 0.001026153564453125s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 40.70774292945862s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.021039485931396484s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 4.3392181396484375e-05s
Believability | Calculation of trust value for instagram.videoobject took 1.2874603271484375e-05s
INFO | --- Analysis for instagram_videoobject took 285.4556782245636s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 9.679794311523438e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 53.48667764663696s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.025582551956176758s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 3.170967102050781e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0012619495391845703s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 5.602836608886719e-05s
Believability | Calculation of trust value for Instance Hub Countries took 1.1920928955078125e-05s
INFO | --- Analysis for instance-hub-countries took 199.58377599716187s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 8.797645568847656e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.40732765197753906s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.021375179290771484s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 4.4345855712890625e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 180.48262119293213s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.38690185546875e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0003752708435058594s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 179.4138731956482s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.021232128143310547s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 4.839897155761719e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 1.621246337890625e-05s
INFO | --- Analysis for instance-hub-organizations took 498.87913274765015s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.363059997558594e-05s
Availability | VoID file availability check for Instance Hub People took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.30487775802612305s
Reputation | Calculation of the PageRank for Instance Hub People took 0.021472454071044922s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub People took 1.239776611328125e-05s
INFO | --- Analysis for instance-hub-people took 31.956230878829956s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 8.511543273925781e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.47231411933898926s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.021021604537963867s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.314018249511719e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 8.58306884765625e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.03507661819458s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.506111145019531e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.306380033493042s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.02199077606201172s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.4809112548828125e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 8.821487426757812e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 1.8595507144927979s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.7206878662109375e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.31922030448913574s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.023463964462280273s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.314018249511719e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 1.430511474609375e-05s
INFO | --- Analysis for instance-hub-us-congressional-districts took 1.8477983474731445s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.744529724121094e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.29820871353149414s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.022707700729370117s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.1948089599609375e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 7.557868957519531e-05s
INFO | --- Analysis for instance-hub-us-crops took 1.8626337051391602s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 8.821487426757812e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.31540966033935547s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.022621631622314453s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.314018249511719e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 1.1920928955078125e-05s
INFO | --- Analysis for instance-hub-us-federal-agencies took 1.7580125331878662s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 8.726119995117188e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.38288283348083496s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.021639585494995117s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.7670135498046875e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 1.239776611328125e-05s
INFO | --- Analysis for instance-hub-us-states-and-territories took 1.9204254150390625s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 0.00010538101196289062s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.33184051513671875s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.021064281463623047s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.2901763916015625e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 1.716139316558838s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 30.65288734436035s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.3624742031097412s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.02113795280456543s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.00543212890625e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.2874603271484375e-05s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 72.73108434677124s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.560585021972656e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.3349893093109131s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.3286898136138916s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.022637367248535156s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0010519027709960938s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00011968612670898438s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for interactivemaps-gnoss took 7.706700801849365s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 0.8477380275726318s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.31852006912231445s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.02154684066772461s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.075599670410156e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 1.1920928955078125e-05s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.8466484546661377s
Availability | SPARQL endpoint availability check for intervalue took 0.15499305725097656s
Availability | VoID file availability check for intervalue took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for intervalue took 0.31278085708618164s
Reputation | Calculation of the PageRank for intervalue took 0.021002769470214844s
Interlinking | Calculation of Degree of Connection for intervalue took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for intervalue took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.747245788574219e-05s
Believability | Calculation of trust value for intervalue took 1.1444091796875e-05s
INFO | --- Analysis for intervalue took 1.9003267288208008s
Availability | SPARQL endpoint availability check for Inztrow took 8.702278137207031e-05s
Availability | VoID file availability check for Inztrow took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for Inztrow took 1.2448060512542725s
Reputation | Calculation of the PageRank for Inztrow took 0.027924537658691406s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0013885498046875s
Interlinking | Calculation of Clustering coefficient for Inztrow took 4.4345855712890625e-05s
Believability | Calculation of trust value for Inztrow took 1.1444091796875e-05s
INFO | --- Analysis for Inztrow took 4.23714280128479s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 5.2928924560546875e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.3438889980316162s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.02219414710998535s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for ipbes took 3.5578067302703857s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 9.012222290039062e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.33806538581848145s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02224254608154297s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.935264587402344e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.1682510375976562e-05s
INFO | --- Analysis for iptc-newscodes took 4.554443359375s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 60.059903144836426s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 5.5115790367126465s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.021494150161743164s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 2.8848648071289062e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.1205673217773438e-05s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 155.73841285705566s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 0.5852172374725342s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.42479443550109863s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007424354553222656s
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.2636184692382812e-05s
INFO | --- Analysis for iserve took 6.963458061218262s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.294017791748047s
Availability | VoID file availability check for ISIC V4 took 0.0008807182312011719s
Completeness | Calculation of interlinking completeness for ISIC V4 took 1.122046947479248s
Reputation | Calculation of the PageRank for ISIC V4 took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.4332275390625e-05s
Believability | Calculation of trust value for ISIC V4 took 9.059906005859375e-06s
INFO | --- Analysis for isic-v4 took 104.659592628479s
Availability | SPARQL endpoint availability check for Isidore took 0.9166357517242432s
Availability | VoID file availability check for Isidore took 0.0003833770751953125s
Completeness | Calculation of interlinking completeness for Isidore took 0.3796985149383545s
Reputation | Calculation of the PageRank for Isidore took 0.024545669555664062s
Interlinking | Calculation of Degree of Connection for Isidore took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0012748241424560547s
Interlinking | Calculation of Clustering coefficient for Isidore took 4.315376281738281e-05s
Believability | Calculation of trust value for Isidore took 1.2874603271484375e-05s
INFO | --- Analysis for isidore took 6.090410470962524s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 8.797645568847656e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.00032401084899902344s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.38918113708496094s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.021672725677490234s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.534027099609375e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 8.58306884765625e-06s
INFO | --- Analysis for isil-dbpedia took 2.5032196044921875s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 8.749961853027344e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.31023621559143066s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.021407127380371094s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.123283386230469e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 1.1444091796875e-05s
INFO | --- Analysis for iso-3166-2-data took 7.461831331253052s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 8.940696716308594e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0009911060333251953s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 1.5940284729003906s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.021397113800048828s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.552436828613281e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.0967254638671875e-05s
INFO | --- Analysis for iso-639-oasis took 4.227558374404907s
Availability | SPARQL endpoint availability check for ISOcat took 9.274482727050781e-05s
Availability | VoID file availability check for ISOcat took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for ISOcat took 0.29827237129211426s
Reputation | Calculation of the PageRank for ISOcat took 0.021001815795898438s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.365776062011719e-05s
Believability | Calculation of trust value for ISOcat took 8.106231689453125e-06s
INFO | --- Analysis for isocat took 9.254831552505493s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 0.0001838207244873047s
Availability | VoID file availability check for ISOcat-metadata took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 1.5841615200042725s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02254629135131836s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0009379386901855469s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 4.076957702636719e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.3113021850585938e-05s
INFO | --- Analysis for isocat-metadata took 7.020334959030151s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.1228325366973877s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0006020069122314453s
Extra | Recovery of all triples for ISPRA - Mitigation measures in Italy for national soil protection took 5.5458033084869385s
Performance | Total latancy measurement for ISPRA - Mitigation measures in Italy for national soil protection took 0.3529651165008545s
Amount of data | Number of triples check for ISPRA - Mitigation measures in Italy for national soil protection took 0.15778207778930664s
Interoperability | New terms check for ISPRA - Mitigation measures in Italy for national soil protection took 3.030669689178467s
Versatility | Languages check for ISPRA - Mitigation measures in Italy for national soil protection took 90.2268295288086s
Interpretability | Number of blank nodes check for ISPRA - Mitigation measures in Italy for national soil protection took 0.09373235702514648s
Security | Check HTTPS for ISPRA - Mitigation measures in Italy for national soil protection took 0.03550410270690918s
Interpretability | RDF structures check for ISPRA - Mitigation measures in Italy for national soil protection took 0.11933326721191406s
Versatility | Serialization formats check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0918731689453125s
Availability | RDF dump link check for ISPRA - Mitigation measures in Italy for national soil protection took 0.08765125274658203s
License | MR license check for ISPRA - Mitigation measures in Italy for national soil protection took 0.1377561092376709s
License | HR license check for ISPRA - Mitigation measures in Italy for national soil protection took 91.21815824508667s
Amount of data | Number of property check for ISPRA - Mitigation measures in Italy for national soil protection took 0.09124183654785156s
Understandability | Number of label check for ISPRA - Mitigation measures in Italy for national soil protection took 4.39900279045105s
Understandability | URI regex check for ISPRA - Mitigation measures in Italy for national soil protection took 0.31029176712036133s
Understandability | Vocabs check for ISPRA - Mitigation measures in Italy for national soil protection took 0.1270143985748291s
Verifiability | Authors check for ISPRA - Mitigation measures in Italy for national soil protection took 0.13739609718322754s
Verifiability | Publishers check for ISPRA - Mitigation measures in Italy for national soil protection took 0.10161876678466797s
Performance | Throughput check for ISPRA - Mitigation measures in Italy for national soil protection took 10.372103214263916s
Amount of data | Check the number of entities for ISPRA - Mitigation measures in Italy for national soil protection took 9.298324584960938e-05s
Verifiability | Contribs. check for ISPRA - Mitigation measures in Italy for national soil protection took 0.1280820369720459s
Interlinking | sameAs chians check for ISPRA - Mitigation measures in Italy for national soil protection took 0.07834482192993164s
Interlinking | skos check for ISPRA - Mitigation measures in Italy for national soil protection took 0.41455650329589844s
Interlinking | skos check for ISPRA - Mitigation measures in Italy for national soil protection took 0.39249730110168457s
Timeliness | dataset update frequency check for ISPRA - Mitigation measures in Italy for national soil protection took 0.15798139572143555s
Currency | Creation date check for ISPRA - Mitigation measures in Italy for national soil protection took 0.4265468120574951s
Currency | Modification date check for ISPRA - Mitigation measures in Italy for national soil protection took 0.10370874404907227s
Rep.Conc. | URIs length for ISPRA - Mitigation measures in Italy for national soil protection took 13.077057838439941s
Interoperability | New vocabularies check for ISPRA - Mitigation measures in Italy for national soil protection took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - Mitigation measures in Italy for national soil protection took 0.08006048202514648s
Accuracy | Check Functional Property for ISPRA - Mitigation measures in Italy for national soil protection took 0.08750343322753906s
Accuracy | Check Inverse Functional Property for ISPRA - Mitigation measures in Italy for national soil protection took 0.08482956886291504s
Accuracy | Check Empty annotation labels for ISPRA - Mitigation measures in Italy for national soil protection took 2.8977842330932617s
Accuracy | Check White space in annotation for ISPRA - Mitigation measures in Italy for national soil protection took 0.31731224060058594s
Accuracy | Check Datatype consistency for ISPRA - Mitigation measures in Italy for national soil protection took 0.27840399742126465s
Consistency | Disjoint class check for ISPRA - Mitigation measures in Italy for national soil protection took 0.08005952835083008s
Consistency | Check Misplaced properties for ISPRA - Mitigation measures in Italy for national soil protection took 9.047374725341797s
Consistency | Misplaced classes for ISPRA - Mitigation measures in Italy for national soil protection took 0.9553508758544922s
Consistency | Check Ontology hijacking for ISPRA - Mitigation measures in Italy for national soil protection took 2.8713998794555664s
Consistency | Check Invalid usage of undefined classes for ISPRA - Mitigation measures in Italy for national soil protection took 1.368844747543335s
Consistency | Check Invalid usage of undefined properties for ISPRA - Mitigation measures in Italy for national soil protection took 10.293197631835938s
Conciseness | Check Extensional conciseness for ISPRA - Mitigation measures in Italy for national soil protection took 0.3148159980773926s
Conciseness | Check Intensional conciseness for ISPRA - Mitigation measures in Italy for national soil protection took 0.08395075798034668s
Security | Sign check for ISPRA - Mitigation measures in Italy for national soil protection took 0.09495997428894043s
Availability | Check URIs Dereferenciability for ISPRA - Mitigation measures in Italy for national soil protection took 16.04094171524048s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 1.3664312362670898s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.028384685516357422s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 4.1961669921875e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - Mitigation measures in Italy for national soil protection took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 1.1205673217773438e-05s
INFO | --- Analysis for ispra-lod-ihi took 471.80064392089844s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.06615829467773438s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007226467132568359s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.323146820068359s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.30236029624938965s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16751360893249512s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.0202205181121826s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.17764282226562s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08042621612548828s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.03559446334838867s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10726475715637207s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09905600547790527s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0848081111907959s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1542508602142334s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 92.92485666275024s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08573174476623535s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.643562078475952s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27779340744018555s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1161501407623291s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11800217628479004s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07974839210510254s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.311662197113037s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.179115295410156e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1283564567565918s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08897280693054199s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4864823818206787s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4375650882720947s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12759613990783691s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31940388679504395s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09063911437988281s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.013195037841797s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07787013053894043s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09261250495910645s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1204843521118164s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.9265682697296143s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3161947727203369s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27936863899230957s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08632993698120117s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.01749873161316s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9275374412536621s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.898696184158325s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3900113105773926s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.34835147857666s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3200490474700928s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07952165603637695s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11273694038391113s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.88840937614441s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2347230911254883s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.021697998046875s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.5762786865234375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3113021850585938e-05s
INFO | --- Analysis for ispra-lod-place took 461.0964434146881s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.05520820617675781s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0004467964172363281s
Extra | Recovery of all triples for ISPRA - The Italian National Tide Gauge Network (RMN) took 5.196560859680176s
Performance | Total latancy measurement for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.3041250705718994s
Amount of data | Number of triples check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.15184831619262695s
Interoperability | New terms check for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.039024829864502s
Versatility | Languages check for ISPRA - The Italian National Tide Gauge Network (RMN) took 93.4062762260437s
Interpretability | Number of blank nodes check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.08538126945495605s
Security | Check HTTPS for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0364527702331543s
Interpretability | RDF structures check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.1029670238494873s
Versatility | Serialization formats check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.08240199089050293s
Availability | RDF dump link check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.10469460487365723s
License | MR license check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.14584994316101074s
License | HR license check for ISPRA - The Italian National Tide Gauge Network (RMN) took 92.8976502418518s
Amount of data | Number of property check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.08190011978149414s
Understandability | Number of label check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.433817148208618s
Understandability | URI regex check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2735109329223633s
Understandability | Vocabs check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.11844491958618164s
Verifiability | Authors check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.1227726936340332s
Verifiability | Publishers check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.08005356788635254s
Performance | Throughput check for ISPRA - The Italian National Tide Gauge Network (RMN) took 10.42756700515747s
Amount of data | Check the number of entities for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0005371570587158203s
Verifiability | Contribs. check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.11428260803222656s
Interlinking | sameAs chians check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.07984638214111328s
Interlinking | skos check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.3641026020050049s
Interlinking | skos check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.34323549270629883s
Timeliness | dataset update frequency check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.17339730262756348s
Currency | Creation date check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.3342165946960449s
Currency | Modification date check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.09166598320007324s
Rep.Conc. | URIs length for ISPRA - The Italian National Tide Gauge Network (RMN) took 13.058173656463623s
Interoperability | New vocabularies check for ISPRA - The Italian National Tide Gauge Network (RMN) took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0774083137512207s
Accuracy | Check Functional Property for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.08272433280944824s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.08251166343688965s
Accuracy | Check Empty annotation labels for ISPRA - The Italian National Tide Gauge Network (RMN) took 2.769221067428589s
Accuracy | Check White space in annotation for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.31719040870666504s
Accuracy | Check Datatype consistency for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2797074317932129s
Consistency | Disjoint class check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.07608485221862793s
Consistency | Check Misplaced properties for ISPRA - The Italian National Tide Gauge Network (RMN) took 9.010717868804932s
Consistency | Misplaced classes for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.9697458744049072s
Consistency | Check Ontology hijacking for ISPRA - The Italian National Tide Gauge Network (RMN) took 2.886780261993408s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.3831744194030762s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian National Tide Gauge Network (RMN) took 10.343931674957275s
Conciseness | Check Extensional conciseness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.3205440044403076s
Conciseness | Check Intensional conciseness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.14371657371520996s
Security | Sign check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.093017578125s
Availability | Check URIs Dereferenciability for ISPRA - The Italian National Tide Gauge Network (RMN) took 8.291017293930054s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.157731533050537s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.026906251907348633s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0010898113250732422s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.3113021850585938e-05s
INFO | --- Analysis for ispra-lod-rmn took 455.5584077835083s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05724668502807617s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0004677772521972656s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.339219093322754s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.314685583114624s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.15671920776367188s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 3.015594482421875s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.90374970436096s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.08037757873535156s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.034613609313964844s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.10421562194824219s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.08271408081054688s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.08907580375671387s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.12903285026550293s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.88052010536194s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.12063884735107422s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 4.441601514816284s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.30609583854675293s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.2363569736480713s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.13418078422546387s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08034420013427734s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.412061214447021s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 9.703636169433594e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.12132000923156738s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.08429765701293945s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.3593180179595947s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.3398158550262451s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.1252143383026123s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.32047033309936523s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.11477112770080566s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 12.891135215759277s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08070015907287598s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.08963775634765625s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.08325529098510742s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.5496184825897217s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.31316518783569336s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27275681495666504s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.07558774948120117s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 8.92578411102295s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9472863674163818s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.9311323165893555s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.42386794090271s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.241823673248291s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.31287384033203125s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.08441901206970215s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.09437370300292969s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 17.48580813407898s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 2.2339699268341064s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021632909774780273s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 6.198883056640625e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.3113021850585938e-05s
INFO | --- Analysis for ispra-lod-ron took 458.92030906677246s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 0.05646395683288574s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.00038504600524902344s
Extra | Recovery of all triples for ISPRA - Soil Consumption Indicators in Italy took 5.3955397605896s
Performance | Total latancy measurement for ISPRA - Soil Consumption Indicators in Italy took 0.30985307693481445s
Amount of data | Number of triples check for ISPRA - Soil Consumption Indicators in Italy took 0.16358494758605957s
Interoperability | New terms check for ISPRA - Soil Consumption Indicators in Italy took 3.018718719482422s
Versatility | Languages check for ISPRA - Soil Consumption Indicators in Italy took 91.84996891021729s
Interpretability | Number of blank nodes check for ISPRA - Soil Consumption Indicators in Italy took 0.07960700988769531s
Security | Check HTTPS for ISPRA - Soil Consumption Indicators in Italy took 0.03350400924682617s
Interpretability | RDF structures check for ISPRA - Soil Consumption Indicators in Italy took 0.10586786270141602s
Versatility | Serialization formats check for ISPRA - Soil Consumption Indicators in Italy took 0.0819692611694336s
Availability | RDF dump link check for ISPRA - Soil Consumption Indicators in Italy took 0.08307313919067383s
License | MR license check for ISPRA - Soil Consumption Indicators in Italy took 0.14434576034545898s
License | HR license check for ISPRA - Soil Consumption Indicators in Italy took 92.52056765556335s
Amount of data | Number of property check for ISPRA - Soil Consumption Indicators in Italy took 0.08150911331176758s
Understandability | Number of label check for ISPRA - Soil Consumption Indicators in Italy took 4.357762098312378s
Understandability | URI regex check for ISPRA - Soil Consumption Indicators in Italy took 0.3045778274536133s
Understandability | Vocabs check for ISPRA - Soil Consumption Indicators in Italy took 0.13535094261169434s
Verifiability | Authors check for ISPRA - Soil Consumption Indicators in Italy took 0.12665295600891113s
Verifiability | Publishers check for ISPRA - Soil Consumption Indicators in Italy took 0.09312725067138672s
Performance | Throughput check for ISPRA - Soil Consumption Indicators in Italy took 10.37094235420227s
Amount of data | Check the number of entities for ISPRA - Soil Consumption Indicators in Italy took 0.0005991458892822266s
Verifiability | Contribs. check for ISPRA - Soil Consumption Indicators in Italy took 0.12144970893859863s
Interlinking | sameAs chians check for ISPRA - Soil Consumption Indicators in Italy took 0.08014988899230957s
Interlinking | skos check for ISPRA - Soil Consumption Indicators in Italy took 0.409984827041626s
Interlinking | skos check for ISPRA - Soil Consumption Indicators in Italy took 0.37613558769226074s
Timeliness | dataset update frequency check for ISPRA - Soil Consumption Indicators in Italy took 0.12139248847961426s
Currency | Creation date check for ISPRA - Soil Consumption Indicators in Italy took 0.3213522434234619s
Currency | Modification date check for ISPRA - Soil Consumption Indicators in Italy took 0.09508872032165527s
Rep.Conc. | URIs length for ISPRA - Soil Consumption Indicators in Italy took 13.005516290664673s
Interoperability | New vocabularies check for ISPRA - Soil Consumption Indicators in Italy took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - Soil Consumption Indicators in Italy took 0.08481168746948242s
Accuracy | Check Functional Property for ISPRA - Soil Consumption Indicators in Italy took 0.159501314163208s
Accuracy | Check Inverse Functional Property for ISPRA - Soil Consumption Indicators in Italy took 0.0883488655090332s
Accuracy | Check Empty annotation labels for ISPRA - Soil Consumption Indicators in Italy took 2.605858325958252s
Accuracy | Check White space in annotation for ISPRA - Soil Consumption Indicators in Italy took 0.31632518768310547s
Accuracy | Check Datatype consistency for ISPRA - Soil Consumption Indicators in Italy took 0.2795567512512207s
Consistency | Disjoint class check for ISPRA - Soil Consumption Indicators in Italy took 0.08052587509155273s
Consistency | Check Misplaced properties for ISPRA - Soil Consumption Indicators in Italy took 9.067928314208984s
Consistency | Misplaced classes for ISPRA - Soil Consumption Indicators in Italy took 0.9380300045013428s
Consistency | Check Ontology hijacking for ISPRA - Soil Consumption Indicators in Italy took 3.1296162605285645s
Consistency | Check Invalid usage of undefined classes for ISPRA - Soil Consumption Indicators in Italy took 1.391707420349121s
Consistency | Check Invalid usage of undefined properties for ISPRA - Soil Consumption Indicators in Italy took 10.21914792060852s
Conciseness | Check Extensional conciseness for ISPRA - Soil Consumption Indicators in Italy took 0.31666088104248047s
Conciseness | Check Intensional conciseness for ISPRA - Soil Consumption Indicators in Italy took 0.08178520202636719s
Security | Sign check for ISPRA - Soil Consumption Indicators in Italy took 0.1005563735961914s
Availability | Check URIs Dereferenciability for ISPRA - Soil Consumption Indicators in Italy took 17.472719192504883s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 34.09024500846863s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.021121978759765625s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - Soil Consumption Indicators in Italy took 1.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 1.239776611328125e-05s
INFO | --- Analysis for ispra-lod-sc took 502.72399282455444s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6700096130371094s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 35.97711420059204s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.021138668060302734s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 0.00010585784912109375s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for issa-agritrop took 231.32477259635925s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 9.298324584960938e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.3805053234100342s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.022347450256347656s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.123283386230469e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.2874603271484375e-05s
INFO | --- Analysis for ISSN:0080-3626 took 216.3546223640442s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 9.274482727050781e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.39452576637268066s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.027338743209838867s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0011088848114013672s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 4.363059997558594e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.239776611328125e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 121.082852602005s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 0.00011754035949707031s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.29489612579345703s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.02129507064819336s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.000997304916381836s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.62396240234375e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.1682510375976562e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 61.828608989715576s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.588597059249878s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 119.7400496006012s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.021425962448120117s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 9.822845458984375e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 1.1444091796875e-05s
INFO | --- Analysis for istat-immigration took 360.7814848423004s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 8.630752563476562e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 119.68705463409424s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.314018249511719e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 1.239776611328125e-05s
INFO | --- Analysis for istat-immigrazione took 352.6639382839203s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.1479320526123047s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.36238861083984375s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.021703481674194336s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.886222839355469e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 8.821487426757812e-06s
INFO | --- Analysis for it-aifa-drug-prices took 82.60454726219177s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.815899133682251s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.356050968170166s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.022579193115234375s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0008249282836914062s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 8.58306884765625e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.3113021850585938e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 20.36692762374878s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 24.936835050582886s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.44826674461364746s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.02099156379699707s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.7670135498046875e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 1.2636184692382812e-05s
INFO | --- Analysis for iucr-acta-cryst-e took 61.060542821884155s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 8.678436279296875e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.31177783012390137s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.021237611770629883s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.0994415283203125e-05s
Believability | Calculation of trust value for IWMI Research Reports took 1.2159347534179688e-05s
INFO | --- Analysis for iwmi-research-reports took 3.1900787353515625s
Availability | SPARQL endpoint availability check for IWN took 4.5299530029296875e-05s
Availability | VoID file availability check for IWN took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for IWN took 0.3991076946258545s
Reputation | Calculation of the PageRank for IWN took 0.02115011215209961s
Interlinking | Calculation of Degree of Connection for IWN took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for IWN took 3.6716461181640625e-05s
Believability | Calculation of trust value for IWN took 1.33514404296875e-05s
INFO | --- Analysis for iwn took 2.221798896789551s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 0.056089162826538086s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.30945372581481934s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02263617515563965s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.002124786376953125s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.314018249511719e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 1.1444091796875e-05s
INFO | --- Analysis for j-global-knowledge took 1.8605504035949707s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 393.50591111183167s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.0007929801940917969s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 20.80021643638611s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.022757530212402344s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.719329833984375e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 1.4066696166992188e-05s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 622.1148662567139s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 0.3983440399169922s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 10.731201648712158s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.021129608154296875s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.0558319091796875e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.2636184692382812e-05s
INFO | --- Analysis for jamendo-dbtune took 106.25534081459045s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 9.059906005859375e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 1.266819953918457s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.5182359218597412s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.021090269088745117s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 5.054473876953125e-05s
Interoperability | Check the re-using of existing vocabs for National Radioactivity Stat as Linked Data took 30.982934713363647s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for japan-radioactivity-stat took 91.04306864738464s
Availability | SPARQL endpoint availability check for JEL Classification took 0.000125885009765625s
Availability | VoID file availability check for JEL Classification took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.31021833419799805s
Reputation | Calculation of the PageRank for JEL Classification took 0.02241659164428711s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.6716461181640625e-05s
Believability | Calculation of trust value for JEL Classification took 1.2874603271484375e-05s
INFO | --- Analysis for jel-classification took 77.0316550731659s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 0.42302513122558594s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 11.777031660079956s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.8623809814453125e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.2159347534179688e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 37.62545156478882s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.4361889362335s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.19479918479919434s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 47.47198033332825s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.02183985710144043s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0008604526519775391s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.654594421386719e-05s
Interoperability | Check the re-using of existing vocabs for JITA Classification System of Library and Information Science took 8.40296483039856s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.3113021850585938e-05s
INFO | --- Analysis for jita took 456.75634384155273s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.9114227294921875e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0003914833068847656s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.29373741149902344s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.029445648193359375s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0012836456298828125s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 5.459785461425781e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 1.1920928955078125e-05s
INFO | --- Analysis for jmdict took 150.1476707458496s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.052244663238525s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0007970333099365234s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 29.12077760696411s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02337956428527832s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 0.00010609626770019531s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.239776611328125e-05s
INFO | --- Analysis for john-goodwins-family-tree took 214.5655550956726s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 9.202957153320312e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 1.6956424713134766s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02253890037536621s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.00086212158203125s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 4.220008850097656e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.1682510375976562e-05s
INFO | --- Analysis for jp-cos took 99.88542819023132s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 8.606910705566406e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0007681846618652344s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.8747282028198242s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.021583080291748047s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.76837158203125e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.2159347534179688e-05s
INFO | --- Analysis for jp-textbook took 52.90652251243591s
Availability | SPARQL endpoint availability check for JRC-Names took 2.1639485359191895s
Availability | VoID file availability check for JRC-Names took 0.0007104873657226562s
Completeness | Calculation of interlinking completeness for JRC-Names took 35.43878960609436s
Reputation | Calculation of the PageRank for JRC-Names took 0.02207016944885254s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0008368492126464844s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.409385681152344e-05s
Believability | Calculation of trust value for JRC-Names took 1.3113021850585938e-05s
INFO | --- Analysis for jrc-names-ec took 129.05664730072021s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 40.33067297935486s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 13.357923984527588s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.022696733474731445s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 8.225440979003906e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.239776611328125e-05s
INFO | --- Analysis for jrc-names-mlode took 287.32552886009216s
Availability | SPARQL endpoint availability check for JudaicaLink took 9.870529174804688e-05s
Availability | VoID file availability check for JudaicaLink took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for JudaicaLink took 33.745418310165405s
Reputation | Calculation of the PageRank for JudaicaLink took 0.021439313888549805s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00012040138244628906s
Believability | Calculation of trust value for JudaicaLink took 1.2636184692382812e-05s
INFO | --- Analysis for judaicalink took 247.17273950576782s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 9.322166442871094e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.2923715114593506s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.023718833923339844s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 2.86102294921875e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 1.239776611328125e-05s
INFO | --- Analysis for kaist-silver-standard-corpus took 137.9349148273468s
Availability | SPARQL endpoint availability check for KAKEN took 9.679794311523438e-05s
Availability | VoID file availability check for KAKEN took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for KAKEN took 51.371604442596436s
Reputation | Calculation of the PageRank for KAKEN took 0.021091222763061523s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.9577484130859375e-05s
Believability | Calculation of trust value for KAKEN took 1.239776611328125e-05s
INFO | --- Analysis for kaken took 462.88411712646484s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06110382080078125s
Availability | VoID file availability check for Kallikratis municipalities took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 60.00688934326172s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.021169662475585938s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.942054748535156e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 1.3589859008789062e-05s
INFO | --- Analysis for kallikratis-municipalities took 300.073792219162s
Availability | SPARQL endpoint availability check for Openflights Routes took 8.606910705566406e-05s
Availability | VoID file availability check for Openflights Routes took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Openflights Routes took 119.68206596374512s
Reputation | Calculation of the PageRank for Openflights Routes took 0.021688461303710938s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.528594970703125e-05s
Believability | Calculation of trust value for Openflights Routes took 7.867813110351562e-06s
INFO | --- Analysis for kasabi-openflights-routes took 180.61515927314758s
Availability | SPARQL endpoint availability check for EU Soccer League took 8.7738037109375e-05s
Availability | VoID file availability check for EU Soccer League took 0.0003838539123535156s
Completeness | Calculation of interlinking completeness for EU Soccer League took 180.12235951423645s
Reputation | Calculation of the PageRank for EU Soccer League took 0.021854877471923828s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 4.100799560546875e-05s
Believability | Calculation of trust value for EU Soccer League took 1.3113021850585938e-05s
INFO | --- Analysis for KG:Course_Submission took 447.03566098213196s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 9.012222290039062e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.32174015045166016s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.023082256317138672s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 2.86102294921875e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 6.699562072753906e-05s
INFO | --- Analysis for KING took 15.411447286605835s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 8.749961853027344e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.31183409690856934s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.02114582061767578s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 7.033348083496094e-05s
Believability | Calculation of trust value for Klappstuhlclub took 9.059906005859375e-06s
INFO | --- Analysis for klappstuhlclub took 12.009645700454712s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.849243640899658s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.30400705337524414s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.023217201232910156s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.127357482910156e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.2874603271484375e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 22.855396032333374s
Availability | SPARQL endpoint availability check for Knowledge Forest took 8.821487426757812e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.30744504928588867s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.7894973754882812e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.2159347534179688e-05s
INFO | --- Analysis for knowledge-map took 2.9317569732666016s
Availability | SPARQL endpoint availability check for Knowledge Forest took 8.821487426757812e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.33535027503967285s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02106475830078125s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.765655517578125e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.1444091796875e-05s
INFO | --- Analysis for KnowledgeFusion took 1.8984203338623047s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 8.726119995117188e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.45073366165161133s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.023955821990966797s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 7.009506225585938e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.33514404296875e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 13.728249311447144s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 20.81004786491394s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.8250441551208496s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 1.1444091796875e-05s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 56.12952136993408s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.863739013671875e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.597116470336914s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.021085500717163086s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.7179718017578125e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.2159347534179688e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 16.527465343475342s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 0.3336300849914551s
Availability | VoID file availability check for Korean Traditional Recipes took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.4749925136566162s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.022623062133789062s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.147125244140625e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 1.3113021850585938e-05s
INFO | --- Analysis for ktr took 2.450242519378662s
Availability | SPARQL endpoint availability check for Informatics Studies took 9.965896606445312e-05s
Availability | VoID file availability check for Informatics Studies took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Informatics Studies took 1.5235705375671387s
Reputation | Calculation of the PageRank for Informatics Studies took 0.021422624588012695s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.7894973754882812e-05s
Believability | Calculation of trust value for Informatics Studies took 1.1920928955078125e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 5.5297691822052s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.07037973403930664s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.3184695243835449s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.022072553634643555s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0011653900146484375s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 4.696846008300781e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 9.298324584960938e-06s
INFO | --- Analysis for kupkb took 9.41499662399292s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 0.11199283599853516s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.30696773529052734s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.02119278907775879s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0008497238159179688s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.1948089599609375e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 1.239776611328125e-05s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.1542162895202637s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 9.818124294281006s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.32572007179260254s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.023191452026367188s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.869171142578125e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.239776611328125e-05s
INFO | --- Analysis for l3s-dblp took 48.139293909072876s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.033337354660034s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.348468542098999s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.021309852600097656s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.818771362304688e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for lak-dataset took 47.186784982681274s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.2210400104522705s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005860328674316406s
Extra | Recovery of all triples for  Language Name Authority List  took 172.7246482372284s
Performance | Total latancy measurement for  Language Name Authority List  took 0.5850365161895752s
Amount of data | Number of triples check for  Language Name Authority List  took 46.67023706436157s
Interoperability | New terms check for  Language Name Authority List  took 51.721884965896606s
Versatility | Languages check for  Language Name Authority List  took 300.1170904636383s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 14.51337194442749s
Security | Check HTTPS for  Language Name Authority List  took 0.3907284736633301s
Interpretability | RDF structures check for  Language Name Authority List  took 0.28436923027038574s
Versatility | Serialization formats check for  Language Name Authority List  took 0.22336745262145996s
Availability | RDF dump link check for  Language Name Authority List  took 0.24647951126098633s
License | MR license check for  Language Name Authority List  took 0.4647502899169922s
License | HR license check for  Language Name Authority List  took 300.08967781066895s
Amount of data | Number of property check for  Language Name Authority List  took 0.18602514266967773s
Understandability | Number of label check for  Language Name Authority List  took 1.806077241897583s
Understandability | URI regex check for  Language Name Authority List  took 0.39732813835144043s
Understandability | Vocabs check for  Language Name Authority List  took 0.09543824195861816s
Verifiability | Authors check for  Language Name Authority List  took 0.16018962860107422s
Verifiability | Publishers check for  Language Name Authority List  took 0.18407893180847168s
Performance | Throughput check for  Language Name Authority List  took 10.609742403030396s
Amount of data | Check the number of entities for  Language Name Authority List  took 0.0001251697540283203s
Verifiability | Contribs. check for  Language Name Authority List  took 0.19036555290222168s
Interlinking | sameAs chians check for  Language Name Authority List  took 8.400647163391113s
Interlinking | skos check for  Language Name Authority List  took 0.18044042587280273s
Interlinking | skos check for  Language Name Authority List  took 0.1389915943145752s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.2472548484802246s
Currency | Creation date check for  Language Name Authority List  took 0.6979894638061523s
Currency | Modification date check for  Language Name Authority List  took 0.16397881507873535s
Rep.Conc. | URIs length for  Language Name Authority List  took 394.94016313552856s
Interoperability | New vocabularies check for  Language Name Authority List  took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.18605899810791016s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.1751720905303955s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.17467212677001953s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.48819637298584s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.100874185562134s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.71175479888916s
Consistency | Disjoint class check for  Language Name Authority List  took 0.12807989120483398s
Consistency | Check Misplaced properties for  Language Name Authority List  took 293.2787353992462s
Consistency | Misplaced classes for  Language Name Authority List  took 8.676757574081421s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 38.126051902770996s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.7622566223144531s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 297.67000675201416s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.3802146911621094s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.3954050540924072s
Security | Sign check for  Language Name Authority List  took 0.45232176780700684s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 16.106217861175537s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 19.612088680267334s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.02121424674987793s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.6689300537109375e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.1920928955078125e-05s
INFO | --- Analysis for language-authority-list took 9974.549092292786s
Availability | SPARQL endpoint availability check for Lark took 182.27175736427307s
Availability | VoID file availability check for Lark took 0.0012416839599609375s
Completeness | Calculation of interlinking completeness for Lark took 1.2009515762329102s
Reputation | Calculation of the PageRank for Lark took 0.02925705909729004s
Interlinking | Calculation of Degree of Connection for Lark took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Lark took 0.0012562274932861328s
Interlinking | Calculation of Clustering coefficient for Lark took 0.0001323223114013672s
Believability | Calculation of trust value for Lark took 1.2636184692382812e-05s
INFO | --- Analysis for LARK took 675.6340596675873s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.4925220012664795s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 1.674621820449829s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.02131175994873047s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for LASLA took 12.462962627410889s
Availability | SPARQL endpoint availability check for LATC Linksets took 0.07636046409606934s
Availability | VoID file availability check for LATC Linksets took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for LATC Linksets took 1.059842824935913s
Reputation | Calculation of the PageRank for LATC Linksets took 0.023186683654785156s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.170967102050781e-05s
Believability | Calculation of trust value for LATC Linksets took 1.3113021850585938e-05s
INFO | --- Analysis for latc-linksets took 9.708041429519653s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.47371339797973633s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0007770061492919922s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 2.562741756439209s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.021159887313842773s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.267692565917969e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.33514404296875e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 11.589424133300781s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.4553065299987793s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.3407266139984131s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.022161483764648438s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0019252300262451172s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 7.534027099609375e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for LatinAffectus took 5.120737314224243s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.4303441047668457s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 1.882563829421997s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.02440810203552246s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0012624263763427734s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 5.507469177246094e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for LatinWordnetLiLa took 7.027941942214966s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 40.04170560836792s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0007996559143066406s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.3375852108001709s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.023540735244750977s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 1.2874603271484375e-05s
INFO | --- Analysis for lcc took 86.02583312988281s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 5.91278076171875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.36762309074401855s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.0001163482666015625s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.33514404296875e-05s
INFO | --- Analysis for lcsh took 6.939373016357422s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.458427429199219e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 1.0005733966827393s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02138209342956543s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.702278137207031e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.3113021850585938e-05s
INFO | --- Analysis for lcsubjects took 4.957146167755127s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 1.0632779598236084s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 17.997615098953247s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.695487976074219e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 1.1920928955078125e-05s
INFO | --- Analysis for ldqm-dbpedia-2016 took 85.39700102806091s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.957238912582397s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.3370656967163086s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02509307861328125s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0021796226501464844s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 0.00012111663818359375s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.1682510375976562e-05s
INFO | --- Analysis for ldt@library took 62.60153555870056s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 0.00010085105895996094s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 10.312024354934692s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.022279977798461914s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.147125244140625e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 1.3113021850585938e-05s
INFO | --- Analysis for learned-genre-ontology-eng took 47.30576944351196s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 9.012222290039062e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.574291467666626s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.022008895874023438s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.9802322387695312e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 1.2159347534179688e-05s
INFO | --- Analysis for learned-genre-ontology-intl took 22.145696878433228s
Availability | SPARQL endpoint availability check for U ime Legije took 4.267692565917969e-05s
Availability | VoID file availability check for U ime Legije took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for U ime Legije took 21.677560567855835s
Reputation | Calculation of the PageRank for U ime Legije took 0.022812843322753906s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0010449886322021484s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.62396240234375e-05s
Believability | Calculation of trust value for U ime Legije took 1.2159347534179688e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 77.82995629310608s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 0.047455549240112305s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.4126737117767334s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.023137569427490234s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.933906555175781e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 1.2159347534179688e-05s
INFO | --- Analysis for legislation-openuplabs took 100.52436900138855s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.4518258571624756s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 59.613043546676636s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.022394895553588867s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 8.749961853027344e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.2874603271484375e-05s
INFO | --- Analysis for LemmaBank took 182.73280262947083s
Availability | SPARQL endpoint availability check for lemonUby took 9.083747863769531e-05s
Availability | VoID file availability check for lemonUby took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for lemonUby took 0.29442811012268066s
Reputation | Calculation of the PageRank for lemonUby took 0.02146434783935547s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.628036499023438e-05s
Believability | Calculation of trust value for lemonUby took 1.33514404296875e-05s
INFO | --- Analysis for lemonuby took 2.920853614807129s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.940696716308594e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.3052074909210205s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.021213054656982422s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.790855407714844e-05s
Believability | Calculation of trust value for LemonWiktionary took 2.384185791015625e-05s
INFO | --- Analysis for lemonwiktionary took 64.17636799812317s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.39927148818969727s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.3231313228607178s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.0212247371673584s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 4.38690185546875e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for LewisShort took 182.07506227493286s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 0.999121904373169s
Availability | VoID file availability check for LEXIN-RDF took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 59.80656147003174s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02473592758178711s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0012373924255371094s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 5.53131103515625e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.5974044799804688e-05s
INFO | --- Analysis for lexin-rdf took 422.843852519989s
Availability | SPARQL endpoint availability check for lexinfo took 9.131431579589844e-05s
Availability | VoID file availability check for lexinfo took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2887861728668213s
Reputation | Calculation of the PageRank for lexinfo took 0.021201372146606445s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for lexinfo took 0.00010609626770019531s
Believability | Calculation of trust value for lexinfo took 1.3113021850585938e-05s
INFO | --- Analysis for lexinfo took 191.41358590126038s
Availability | SPARQL endpoint availability check for Lexvo took 8.893013000488281e-05s
Availability | VoID file availability check for Lexvo took 0.21539068222045898s
Completeness | Calculation of interlinking completeness for Lexvo took 1.5705618858337402s
Reputation | Calculation of the PageRank for Lexvo took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for Lexvo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lexvo took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017881393432617188s
Interoperability | Check the re-using of existing vocabs for Lexvo took 9.676609754562378s
Believability | Calculation of trust value for Lexvo took 1.1444091796875e-05s
INFO | --- Analysis for lexvo took 14.600451469421387s
Availability | SPARQL endpoint availability check for Lexvo.org took 0.00013256072998046875s
Availability | VoID file availability check for Lexvo.org took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.44387078285217285s
Reputation | Calculation of the PageRank for Lexvo.org took 0.02143692970275879s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.462501525878906e-05s
Believability | Calculation of trust value for Lexvo.org took 8.821487426757812e-06s
INFO | --- Analysis for lexvo-org took 2.0123324394226074s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3632524013519287s
Availability | VoID file availability check for LIBRIS took 0.0004627704620361328s
Extra | Recovery of all triples for LIBRIS took 21.444061517715454s
Performance | Total latancy measurement for LIBRIS took 0.7336142063140869s
Amount of data | Number of triples check for LIBRIS took 22.972988605499268s
Interoperability | New terms check for LIBRIS took 16.381407260894775s
Versatility | Languages check for LIBRIS took 0.1961374282836914s
Interpretability | Number of blank nodes check for LIBRIS took 300.0978739261627s
Security | Check HTTPS for LIBRIS took 0.3391697406768799s
Interpretability | RDF structures check for LIBRIS took 0.31236910820007324s
Versatility | Serialization formats check for LIBRIS took 0.20069479942321777s
Availability | RDF dump link check for LIBRIS took 0.1367638111114502s
License | MR license check for LIBRIS took 0.2634425163269043s
License | HR license check for LIBRIS took 0.23738837242126465s
Amount of data | Number of property check for LIBRIS took 0.2534599304199219s
Understandability | Number of label check for LIBRIS took 0.3993642330169678s
Understandability | URI regex check for LIBRIS took 0.2911202907562256s
Understandability | Vocabs check for LIBRIS took 0.13520145416259766s
Verifiability | Authors check for LIBRIS took 0.13372278213500977s
Verifiability | Publishers check for LIBRIS took 0.16994833946228027s
Performance | Throughput check for LIBRIS took 10.965752840042114s
Amount of data | Check the number of entities for LIBRIS took 7.414817810058594e-05s
Verifiability | Contribs. check for LIBRIS took 0.17521953582763672s
Interlinking | sameAs chians check for LIBRIS took 0.1738574504852295s
Interlinking | skos check for LIBRIS took 0.23324918746948242s
Interlinking | skos check for LIBRIS took 0.12762928009033203s
Timeliness | dataset update frequency check for LIBRIS took 0.1374199390411377s
Currency | Creation date check for LIBRIS took 0.4383254051208496s
Currency | Modification date check for LIBRIS took 0.6166069507598877s
Rep.Conc. | URIs length for LIBRIS took 94.35138130187988s
Interoperability | New vocabularies check for LIBRIS took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.20121002197265625s
Accuracy | Check Functional Property for LIBRIS took 0.28570032119750977s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.2127234935760498s
Accuracy | Check Datatype consistency for LIBRIS took 0.2844698429107666s
Consistency | Disjoint class check for LIBRIS took 0.1806323528289795s
Consistency | Check Misplaced properties for LIBRIS took 62.25393271446228s
Consistency | Misplaced classes for LIBRIS took 1.2102108001708984s
Consistency | Check Ontology hijacking for LIBRIS took 6.4966881275177s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3525018692016602s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 63.52531433105469s
Conciseness | Check Extensional conciseness for LIBRIS took 0.3121199607849121s
Conciseness | Check Intensional conciseness for LIBRIS took 0.49873900413513184s
Security | Sign check for LIBRIS took 0.170607328414917s
Availability | Check URIs Dereferenciability for LIBRIS took 17.544787883758545s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.484562873840332s
Reputation | Calculation of the PageRank for LIBRIS took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.965896606445312e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.9073486328125e-06s
Believability | Calculation of trust value for LIBRIS took 1.2159347534179688e-05s
INFO | --- Analysis for libris took 1117.8417541980743s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.060694217681884766s
Availability | VoID file availability check for Public Library of Veroia took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.32065892219543457s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02174234390258789s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0011029243469238281s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 9.131431579589844e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.3828277587890625e-05s
INFO | --- Analysis for libver took 8.093787908554077s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.17345714569091797s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.839977502822876s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02111196517944336s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.273124694824219e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 1.0728836059570312e-05s
INFO | --- Analysis for lichfield-spending took 2.975031614303589s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 9.1552734375e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.39072680473327637s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.218650817871094e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.2159347534179688e-05s
INFO | --- Analysis for lime took 6.703573703765869s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 9.012222290039062e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.48902368545532227s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.4950075149536133s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02277827262878418s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007562637329101562s
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.2636184692382812e-05s
INFO | --- Analysis for lingvoj took 9.567943334579468s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 1.6647489070892334s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.021728992462158203s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.249282836914062e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.3113021850585938e-05s
INFO | --- Analysis for linked-crunchbase took 16.515299797058105s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.9714975357055664s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.9160535335540771s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.022449254989624023s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.001079559326171875s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.083747863769531e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.2874603271484375e-05s
INFO | --- Analysis for linked-drugs took 11.341331958770752s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 8.749961853027344e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 1.363701343536377s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.023594379425048828s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0010874271392822266s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.00011897087097167969s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 8.344650268554688e-06s
INFO | --- Analysis for linked-edgar took 5.9153056144714355s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 9.036064147949219e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.3071932792663574s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.021280765533447266s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 0.00010347366333007812s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.2874603271484375e-05s
INFO | --- Analysis for linked-eurostat took 5.1250832080841064s
Availability | SPARQL endpoint availability check for linked hypernyms took 9.441375732421875e-05s
Availability | VoID file availability check for linked hypernyms took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.40856266021728516s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020838022232055664s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.700920104980469e-05s
Believability | Calculation of trust value for linked hypernyms took 1.239776611328125e-05s
INFO | --- Analysis for linked-hypernyms took 5.25591516494751s
Availability | SPARQL endpoint availability check for Linked Life Data took 246.3325138092041s
Availability | VoID file availability check for Linked Life Data took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.36414670944213867s
Reputation | Calculation of the PageRank for Linked Life Data took 0.02288341522216797s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.001062154769897461s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 6.651878356933594e-05s
Believability | Calculation of trust value for Linked Life Data took 1.1682510375976562e-05s
INFO | --- Analysis for linked-life-data took 730.6362681388855s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.7233412265777588s
Availability | VoID file availability check for Linked Logainm took 0.0003693103790283203s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.3167250156402588s
Reputation | Calculation of the PageRank for Linked Logainm took 0.022813796997070312s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0010569095611572266s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 9.965896606445312e-05s
Believability | Calculation of trust value for Linked Logainm took 1.3113021850585938e-05s
INFO | --- Analysis for linked-logainm took 3.061934232711792s
Availability | SPARQL endpoint availability check for Linked NUTS took 0.00012230873107910156s
Availability | VoID file availability check for Linked NUTS took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2852005958557129s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02133774757385254s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.888938903808594e-05s
Believability | Calculation of trust value for Linked NUTS took 7.3909759521484375e-06s
INFO | --- Analysis for linked-nuts took 121.68553829193115s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 8.392333984375e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 119.98979258537292s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.0213010311126709s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 3.719329833984375e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 1.1682510375976562e-05s
INFO | --- Analysis for linked-open-aalto-data-service took 240.94738149642944s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.3765175342559814s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 120.06339812278748s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.022746801376342773s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0010693073272705078s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 6.532669067382812e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 1.33514404296875e-05s
INFO | --- Analysis for linked-open-camera took 482.4962728023529s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.524908542633057s
Availability | VoID file availability check for Linked Open Commerce took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 180.34276843070984s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.021079301834106445s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.8835067749023438e-05s
INFO | --- Analysis for linked-open-commerce took 787.7082369327545s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.4288089275360107s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 179.70822191238403s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.021547317504882812s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00011157989501953125s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.5974044799804688e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 722.0823860168457s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 0.00011897087097167969s
Availability | VoID file availability check for Linked Open Numbers took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 179.8260498046875s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.02169179916381836s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 0.00010704994201660156s
Believability | Calculation of trust value for Linked Open Numbers took 1.1444091796875e-05s
INFO | --- Analysis for linked-open-numbers took 1079.594467639923s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 9.894371032714844e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 120.30830192565918s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.0233457088470459s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 5.5789947509765625e-05s
Believability | Calculation of trust value for Linked Open Piracy took 1.4066696166992188e-05s
INFO | --- Analysis for linked-open-piracy took 545.8715107440948s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 6.246566772460938e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.0007305145263671875s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 180.1535999774933s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.021267175674438477s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 4.458427429199219e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 1.3589859008789062e-05s
INFO | --- Analysis for linked-open-senate took 1079.7840313911438s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 14.927996397018433s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.4746894836425781s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.021397829055786133s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 5.817413330078125e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.2636184692382812e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 108.71840906143188s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 8.7738037109375e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.4085705280303955s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02149486541748047s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.5762786865234375e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 9.059906005859375e-06s
INFO | --- Analysis for linked-periodicals took 2.1437599658966064s
Availability | SPARQL endpoint availability check for Linked Index took 8.630752563476562e-05s
Availability | VoID file availability check for Linked Index took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Linked Index took 0.30025148391723633s
Reputation | Calculation of the PageRank for Linked Index took 0.021211624145507812s
Interlinking | Calculation of Degree of Connection for Linked Index took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.487701416015625e-05s
Believability | Calculation of trust value for Linked Index took 1.1920928955078125e-05s
INFO | --- Analysis for linked-stockindex took 2.3122596740722656s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.298810243606567s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 2.0690619945526123s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.021732330322265625s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0013589859008789062s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 4.744529724121094e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 7.3909759521484375e-06s
INFO | --- Analysis for linked-structured-product-labels took 21.067677974700928s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.3570997714996338s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0003864765167236328s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.29889917373657227s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.0257108211517334s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0013430118560791016s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 5.030632019042969e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.2874603271484375e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 2.2318904399871826s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.29299783706665s
Availability | VoID file availability check for Linked TCGA took 0.0008347034454345703s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.5216882228851318s
Reputation | Calculation of the PageRank for Linked TCGA took 0.027017593383789062s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.870529174804688e-05s
Believability | Calculation of trust value for Linked TCGA took 1.33514404296875e-05s
INFO | --- Analysis for linked-tcga took 42.29745078086853s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.08487844467163086s
Availability | VoID file availability check for Linked User Feedback took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.31904053688049316s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02411484718322754s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.001186370849609375s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 5.7697296142578125e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.3828277587890625e-05s
INFO | --- Analysis for linked-user-feedback took 2.0170528888702393s
Availability | SPARQL endpoint availability check for USPTO Patent data took 1.0839085578918457s
Availability | VoID file availability check for USPTO Patent data took 0.0013108253479003906s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.32202839851379395s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.021494626998901367s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 0.00010251998901367188s
Believability | Calculation of trust value for USPTO Patent data took 1.1444091796875e-05s
INFO | --- Analysis for linked-uspto-patent-data took 198.66510438919067s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 8.559226989746094e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2887606620788574s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.021538257598876953s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 1.4066696166992188e-05s
INFO | --- Analysis for linked-web-apis took 61.13224172592163s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 8.7738037109375e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0003101825714111328s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.31602907180786133s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.021628379821777344s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.4809112548828125e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 6.246566772460938e-05s
INFO | --- Analysis for linkedarc took 1.6591060161590576s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.06456112861633301s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2717421054840088s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.790855407714844e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.2159347534179688e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 2.1654257774353027s
Availability | SPARQL endpoint availability check for LinkedCT took 3.0577330589294434s
Availability | VoID file availability check for LinkedCT took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for LinkedCT took 60.01577353477478s
Reputation | Calculation of the PageRank for LinkedCT took 0.021589279174804688s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010752677917480469s
Believability | Calculation of trust value for LinkedCT took 7.3909759521484375e-06s
INFO | --- Analysis for linkedct took 246.80075073242188s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.44934678077697754s
Availability | VoID file availability check for LinkedGeoData took 0.0005266666412353516s
Extra | Recovery of all triples for LinkedGeoData took 8.198797702789307s
Performance | Total latancy measurement for LinkedGeoData took 0.7341086864471436s
Amount of data | Number of triples check for LinkedGeoData took 46.33132553100586s
Interoperability | New terms check for LinkedGeoData took 91.15993857383728s
Versatility | Languages check for LinkedGeoData took 180.39059615135193s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.23131322860717773s
Security | Check HTTPS for LinkedGeoData took 0.34335780143737793s
Interpretability | RDF structures check for LinkedGeoData took 0.15872979164123535s
Versatility | Serialization formats check for LinkedGeoData took 0.16845178604125977s
Availability | RDF dump link check for LinkedGeoData took 0.12948846817016602s
License | MR license check for LinkedGeoData took 0.19500517845153809s
License | HR license check for LinkedGeoData took 112.34963655471802s
Amount of data | Number of property check for LinkedGeoData took 0.18019413948059082s
Understandability | Number of label check for LinkedGeoData took 1.5040898323059082s
Understandability | URI regex check for LinkedGeoData took 0.29911231994628906s
Understandability | Vocabs check for LinkedGeoData took 0.1653738021850586s
Verifiability | Authors check for LinkedGeoData took 0.14097118377685547s
Verifiability | Publishers check for LinkedGeoData took 0.13390374183654785s
Performance | Throughput check for LinkedGeoData took 10.70120096206665s
Amount of data | Check the number of entities for LinkedGeoData took 0.06607627868652344s
Verifiability | Contribs. check for LinkedGeoData took 7.343690633773804s
Interlinking | sameAs chians check for LinkedGeoData took 0.21703267097473145s
Interlinking | skos check for LinkedGeoData took 0.23572826385498047s
Interlinking | skos check for LinkedGeoData took 0.1317145824432373s
Timeliness | dataset update frequency check for LinkedGeoData took 0.1678004264831543s
Currency | Creation date check for LinkedGeoData took 0.16851139068603516s
Currency | Modification date check for LinkedGeoData took 4.6451263427734375s
Rep.Conc. | URIs length for LinkedGeoData took 273.34993290901184s
Interoperability | New vocabularies check for LinkedGeoData took 95.05636143684387s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.20183324813842773s
Accuracy | Check Functional Property for LinkedGeoData took 0.14914774894714355s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.13217568397521973s
Accuracy | Check Empty annotation labels for LinkedGeoData took 2.2745018005371094s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15923118591308594s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.1385946273803711s
Consistency | Disjoint class check for LinkedGeoData took 0.1550753116607666s
Consistency | Check Misplaced properties for LinkedGeoData took 181.76023411750793s
Consistency | Misplaced classes for LinkedGeoData took 0.657961368560791s
Consistency | Check Ontology hijacking for LinkedGeoData took 2.9518814086914062s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.3390381336212158s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.37159776687622s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.16383099555969238s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.22821259498596191s
Security | Sign check for LinkedGeoData took 0.1642131805419922s
Availability | Check URIs Dereferenciability for LinkedGeoData took 25.122629404067993s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 179.82975554466248s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021626949310302734s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.0001468658447265625s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 45.24565386772156s
Believability | Calculation of trust value for LinkedGeoData took 1.2636184692382812e-05s
INFO | --- Analysis for linkedgeodata took 28891.49439072609s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 5.14984130859375e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 119.90929388999939s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.022503137588500977s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0008423328399658203s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 4.7206878662109375e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 1.33514404296875e-05s
INFO | --- Analysis for linkedgeodata-aerodromes took 421.3595688343048s
Availability | SPARQL endpoint availability check for LinkedLCCN took 6.450554847717285s
Availability | VoID file availability check for LinkedLCCN took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 59.71337080001831s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.021114587783813477s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010585784912109375s
Believability | Calculation of trust value for LinkedLCCN took 1.3113021850585938e-05s
INFO | --- Analysis for linkedlccn took 80.03385066986084s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 0.0001251697540283203s
Availability | VoID file availability check for LinkedMarkMail took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 59.601837158203125s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.021477222442626953s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0009541511535644531s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 5.841255187988281e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.430511474609375e-05s
INFO | --- Analysis for linkedmarkmail took 360.2404730319977s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 2.873887062072754s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 119.71924662590027s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02138233184814453s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00014710426330566406s
Believability | Calculation of trust value for Linked Movie DataBase took 1.2159347534179688e-05s
INFO | --- Analysis for linkedmdb took 613.1933660507202s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.5306017398834229s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007956027984619141s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 179.91578245162964s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02148723602294922s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 8.487701416015625e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for linkedspending took 780.9032652378082s
Availability | SPARQL endpoint availability check for LinkedStats took 8.654594421386719e-05s
Availability | VoID file availability check for LinkedStats took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for LinkedStats took 120.32182168960571s
Reputation | Calculation of the PageRank for LinkedStats took 0.021685123443603516s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 4.172325134277344e-05s
Believability | Calculation of trust value for LinkedStats took 7.152557373046875e-06s
INFO | --- Analysis for linkedstats took 360.75950741767883s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 8.916854858398438e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.00054931640625s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 119.67138266563416s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.02160930633544922s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 4.363059997558594e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 1.2874603271484375e-05s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 420.65417289733887s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 8.606910705566406e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 120.2936999797821s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.022075891494750977s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.719329833984375e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 1.3589859008789062e-05s
INFO | --- Analysis for linking-open-drug-data took 540.948052406311s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.0700228214263916s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.000377655029296875s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 120.30509543418884s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02999138832092285s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00012183189392089844s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.2636184692382812e-05s
INFO | --- Analysis for linklion took 660.8978343009949s
Availability | SPARQL endpoint availability check for Lion's Den took 9.72747802734375e-05s
Availability | VoID file availability check for Lion's Den took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.3182857036590576s
Reputation | Calculation of the PageRank for Lion's Den took 0.02103114128112793s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.6716461181640625e-05s
Believability | Calculation of trust value for Lion's Den took 1.2874603271484375e-05s
INFO | --- Analysis for lionsden took 301.64455556869507s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 41.46440124511719s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 180.02795481681824s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.021312236785888672s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0008299350738525391s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.817413330078125e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.621246337890625e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 702.9831418991089s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 0.00011157989501953125s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 119.83069372177124s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.021462440490722656s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 5.698204040527344e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 6.794929504394531e-05s
INFO | --- Analysis for livtdm took 959.867089509964s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.9591064453125e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.388763427734375s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.021561384201049805s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.956390380859375e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 1.4543533325195312e-05s
INFO | --- Analysis for livtdm2017 took 241.06450867652893s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 8.392333984375e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.3069286346435547s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 1.2636184692382812e-05s
INFO | --- Analysis for lobi took 1.7478320598602295s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.523404598236084s
Availability | VoID file availability check for lobid-organisations took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for lobid-organisations took 119.68877935409546s
Reputation | Calculation of the PageRank for lobid-organisations took 0.021494388580322266s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.0001087188720703125s
Believability | Calculation of trust value for lobid-organisations took 1.1682510375976562e-05s
INFO | --- Analysis for lobid-organisations took 362.0468783378601s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.48394250869750977s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 120.1637487411499s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.021029949188232422s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00011277198791503906s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.1682510375976562e-05s
INFO | --- Analysis for lobid-resources took 123.08671021461487s
Availability | SPARQL endpoint availability check for Linked Open Colors took 9.894371032714844e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.35032153129577637s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.022953033447265625s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 9.417533874511719e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.4543533325195312e-05s
INFO | --- Analysis for loc took 486.51676869392395s
Availability | SPARQL endpoint availability check for Location Ontology took 0.00012683868408203125s
Availability | VoID file availability check for Location Ontology took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Location Ontology took 60.094308853149414s
Reputation | Calculation of the PageRank for Location Ontology took 0.021754741668701172s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 4.3392181396484375e-05s
Believability | Calculation of trust value for Location Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for Location_Ontology took 604.1692090034485s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 9.417533874511719e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 120.35515093803406s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.021793365478515625s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0008530616760253906s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 4.076957702636719e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.4066696166992188e-05s
INFO | --- Analysis for locv took 649.9377057552338s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.749180793762207s
Availability | VoID file availability check for LOD-a-lot took 0.0008015632629394531s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 180.19392943382263s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.021981239318847656s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 4.1484832763671875e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.2636184692382812e-05s
INFO | --- Analysis for lod-a-lot took 672.4239482879639s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 0.00014328956604003906s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.36758852005004883s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.021233320236206055s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 5.269050598144531e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 1.5497207641601562e-05s
INFO | --- Analysis for lod-it_scuole-italiane took 419.50364089012146s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.00010824203491210938s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 120.03731036186218s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.02150249481201172s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0010340213775634766s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 5.53131103515625e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.4781951904296875e-05s
INFO | --- Analysis for lod-taiwan took 480.0164132118225s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 8.559226989746094e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 119.5509614944458s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.021562576293945312s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 0.00010561943054199219s
Believability | Calculation of trust value for LOD2 Project Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for lod2-project-wiki took 481.7624442577362s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.6988818645477295s
Availability | VoID file availability check for LODAC BDLS took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.3650500774383545s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02133965492248535s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 0.00014972686767578125s
Believability | Calculation of trust value for LODAC BDLS took 1.1682510375976562e-05s
INFO | --- Analysis for lodac-bdls took 310.0765109062195s
Availability | SPARQL endpoint availability check for LODRussia Math took 8.368492126464844e-05s
Availability | VoID file availability check for LODRussia Math took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for LODRussia Math took 179.82148218154907s
Reputation | Calculation of the PageRank for LODRussia Math took 0.021610260009765625s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0008642673492431641s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 3.62396240234375e-05s
Believability | Calculation of trust value for LODRussia Math took 1.3589859008789062e-05s
INFO | --- Analysis for lodrussia-math took 240.90985488891602s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.124641418457031e-05s
Availability | VoID file availability check for LODRussia Nano took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 180.19654297828674s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.021579980850219727s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0008337497711181641s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 4.172325134277344e-05s
Believability | Calculation of trust value for LODRussia Nano took 1.9550323486328125e-05s
INFO | --- Analysis for lodrussia-nano took 899.5423460006714s
Availability | SPARQL endpoint availability check for LODStats took 4.482269287109375e-05s
Availability | VoID file availability check for LODStats took 0.0007772445678710938s
Completeness | Calculation of interlinking completeness for LODStats took 0.3146674633026123s
Reputation | Calculation of the PageRank for LODStats took 0.021941423416137695s
Interlinking | Calculation of Degree of Connection for LODStats took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.62396240234375e-05s
Believability | Calculation of trust value for LODStats took 1.6689300537109375e-05s
INFO | --- Analysis for lodstats took 600.739138841629s
Availability | SPARQL endpoint availability check for LODUM took 0.0001010894775390625s
Availability | VoID file availability check for LODUM took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for LODUM took 120.13997459411621s
Reputation | Calculation of the PageRank for LODUM took 0.022296905517578125s
Interlinking | Calculation of Degree of Connection for LODUM took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0008361339569091797s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.886222839355469e-05s
Believability | Calculation of trust value for LODUM took 1.2159347534179688e-05s
INFO | --- Analysis for lodum took 720.996514081955s
Availability | SPARQL endpoint availability check for lofd took 0.12733006477355957s
Availability | VoID file availability check for lofd took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for lofd took 0.2878260612487793s
Reputation | Calculation of the PageRank for lofd took 0.027812480926513672s
Interlinking | Calculation of Degree of Connection for lofd took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for lofd took 3.790855407714844e-05s
Believability | Calculation of trust value for lofd took 4.553794860839844e-05s
INFO | --- Analysis for lofd took 421.0799148082733s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 270.91115379333496s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.42574238777160645s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.0213778018951416s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.435943603515625e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 1.1920928955078125e-05s
INFO | --- Analysis for loius took 671.5416111946106s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 8.845329284667969e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 180.16668701171875s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02641606330871582s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 5.14984130859375e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 1.3113021850585938e-05s
INFO | --- Analysis for loius-linking-italian-university-statistics took 900.041661977768s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6498067378997803s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 119.78002381324768s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02617669105529785s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 6.222724914550781e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 1.2159347534179688e-05s
INFO | --- Analysis for london-gazette took 781.6369533538818s
Availability | SPARQL endpoint availability check for Weather Stations took 0.00011730194091796875s
Availability | VoID file availability check for Weather Stations took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Weather Stations took 119.8992874622345s
Reputation | Calculation of the PageRank for Weather Stations took 0.023264408111572266s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 0.00011444091796875s
Believability | Calculation of trust value for Weather Stations took 1.1920928955078125e-05s
INFO | --- Analysis for los_metar took 607.0067958831787s
Availability | SPARQL endpoint availability check for Lotico took 0.5758674144744873s
Availability | VoID file availability check for Lotico took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Lotico took 180.35015535354614s
Reputation | Calculation of the PageRank for Lotico took 0.021138429641723633s
Interlinking | Calculation of Degree of Connection for Lotico took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Lotico took 9.560585021972656e-05s
Believability | Calculation of trust value for Lotico took 1.239776611328125e-05s
INFO | --- Analysis for lotico took 662.0851497650146s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.358691930770874s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0006663799285888672s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.7067315578460693s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.9223160743713379s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.130110502243042s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.813805341720581s
Versatility | Languages check for Lower Layer Super Output Areas took 0.570584774017334s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 0.15852689743041992s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.18345022201538086s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.19411873817443848s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.1506211757659912s
Availability | RDF dump link check for Lower Layer Super Output Areas took 47.607248067855835s
License | MR license check for Lower Layer Super Output Areas took 0.6703529357910156s
License | HR license check for Lower Layer Super Output Areas took 30.249109029769897s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.22029519081115723s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.21066975593566895s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.40213656425476074s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.2194206714630127s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.2847309112548828s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.2411513328552246s
Performance | Throughput check for Lower Layer Super Output Areas took 11.443616390228271s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 8.678436279296875e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.2484898567199707s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.19829201698303223s
Interlinking | skos check for Lower Layer Super Output Areas took 0.20908236503601074s
Interlinking | skos check for Lower Layer Super Output Areas took 0.12156176567077637s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.1912379264831543s
Currency | Creation date check for Lower Layer Super Output Areas took 0.13706541061401367s
Currency | Modification date check for Lower Layer Super Output Areas took 0.3832528591156006s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.3437657356262207s
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.14558887481689453s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.13500523567199707s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.13225531578063965s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.13875770568847656s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.5907659530639648s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 0.9938228130340576s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.6780545711517334s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.0001728534698486328s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.4476776123046875s
Security | Sign check for Lower Layer Super Output Areas took 0.14931678771972656s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.34011054039001465s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02531599998474121s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0011320114135742188s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 7.104873657226562e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 2.86102294921875e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.621246337890625e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 1078.9126987457275s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5696327686309814s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007083415985107422s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 107.3342502117157s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9491398334503174s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.476826906204224s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.101356267929077s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.255122423172s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.9972503185272217s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2980499267578125s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6921467781066895s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.31127214431762695s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.776792049407959s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2223696708679s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21850061416625977s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.626032590866089s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1791653633117676s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4909543991088867s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21936869621276855s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.8778481483459473s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.378116369247437s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0001361370086669922s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19745779037475586s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2131650447845459s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4947218894958496s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.46575284004211426s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6925501823425293s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1429376602172852s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24902939796447754s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 147.40854358673096s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18083620071411133s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.42288851737976074s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.40117955207824707s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 47.97215914726257s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.728516101837158s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.676581621170044s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19815897941589355s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.20621228218079s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.529708623886108s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 37.218266248703s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.40614914894104s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.19872045516968s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.969247341156006s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5028908252716064s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.304351568222046s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.556998014450073s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 120.32086229324341s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.022176504135131836s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0008349418640136719s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.6927719116210938e-05s
INFO | --- Analysis for LPIS_(Poland) took 2552.715217113495s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19160890579223633s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0003795623779296875s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 107.44934296607971s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9666752815246582s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.168632745742798s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.026684761047363s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.23144698143005s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.0982537269592285s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.30644989013671875s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.665095329284668s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.37158966064453125s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8075704574584961s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2092242240906s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20998096466064453s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.847804069519043s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3436448574066162s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.532289981842041s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19152259826660156s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.91926646232605s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.148518562316895s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.916854858398438e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18738889694213867s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21300458908081055s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.49733734130859375s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.39490318298339844s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20066332817077637s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1702733039855957s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2591419219970703s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 156.37996339797974s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2105107307434082s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.41671276092529297s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3930385112762451s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 39.46258735656738s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7206640243530273s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.807844638824463s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1968982219696045s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.28338193893433s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.795158863067627s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 30.475526094436646s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.44576096534729s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 87.42937684059143s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.997373580932617s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.42193150520324707s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2651300430297852s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 12.877201795578003s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 120.18098664283752s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02377176284790039s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2423.6821925640106s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 0.00018095970153808594s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0003573894500732422s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 60.29700708389282s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.023092269897460938s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.814697265625e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.2874603271484375e-05s
INFO | --- Analysis for lremap-auth took 62.934974193573s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 8.797645568847656e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 60.30598282814026s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.021370410919189453s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 0.00010943412780761719s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.3113021850585938e-05s
INFO | --- Analysis for lremap-conf took 420.9788053035736s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 9.751319885253906e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.3068549633026123s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.025050878524780273s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.9577484130859375e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.1205673217773438e-05s
INFO | --- Analysis for lremap-ri took 62.1160192489624s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00010275840759277344s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.2946498394012451s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.021574974060058594s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 2.9325485229492188e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.2159347534179688e-05s
INFO | --- Analysis for lremap-sub took 120.91210746765137s
Availability | SPARQL endpoint availability check for LSQ took 0.00011324882507324219s
Availability | VoID file availability check for LSQ took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for LSQ took 120.10650277137756s
Reputation | Calculation of the PageRank for LSQ took 0.0217287540435791s
Interlinking | Calculation of Degree of Connection for LSQ took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for LSQ took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.3855438232421875e-05s
Believability | Calculation of trust value for LSQ took 1.0728836059570312e-05s
INFO | --- Analysis for lsq took 361.7708249092102s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.5891225337982178s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.00036215782165527344s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 59.83944821357727s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02129650115966797s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for LucaniPharsalia took 122.22784924507141s
Availability | SPARQL endpoint availability check for Linked rules took 8.96453857421875e-05s
Availability | VoID file availability check for Linked rules took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for Linked rules took 0.37927889823913574s
Reputation | Calculation of the PageRank for Linked rules took 0.021329641342163086s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked rules took 1.3828277587890625e-05s
INFO | --- Analysis for Luminaires_senlis took 61.55682039260864s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 0.0001163482666015625s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0003638267517089844s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 119.89194846153259s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.02171158790588379s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.7670135498046875e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 9.298324584960938e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 419.66790437698364s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.358790159225464s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.3093433380126953s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.021088600158691406s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.4809112548828125e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.33514404296875e-05s
INFO | --- Analysis for makg took 92.10825753211975s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 0.00015616416931152344s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 119.73351883888245s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.025897502899169922s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0013456344604492188s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 6.365776062011719e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.239776611328125e-05s
INFO | --- Analysis for manchester-university-reading-lists took 483.4477310180664s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 9.632110595703125e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.30707764625549316s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.028564453125s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0012650489807128906s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 5.030632019042969e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.2159347534179688e-05s
INFO | --- Analysis for manish took 61.10977602005005s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 9.012222290039062e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.30899786949157715s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.028334856033325195s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 3.552436828613281e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.001940011978149414s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 6.151199340820312e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 1.4066696166992188e-05s
INFO | --- Analysis for mapa-referencia-bogota took 120.531090259552s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 8.96453857421875e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.3546335697174072s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.021167993545532227s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.075599670410156e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 1.2874603271484375e-05s
INFO | --- Analysis for mapa-referencia-bogota-dc took 1.8417134284973145s
Availability | SPARQL endpoint availability check for MARC Codes List took 0.0001304149627685547s
Availability | VoID file availability check for MARC Codes List took 0.0008378028869628906s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.29658007621765137s
Reputation | Calculation of the PageRank for MARC Codes List took 0.02204155921936035s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012302398681640625s
Believability | Calculation of trust value for MARC Codes List took 1.3113021850585938e-05s
INFO | --- Analysis for marc-codes took 12.383555173873901s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.914138793945312e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 59.57192325592041s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02533102035522461s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0013310909271240234s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 5.53131103515625e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1444091796875e-05s
INFO | --- Analysis for masc took 62.79990196228027s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 8.96453857421875e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.3061347007751465s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.029480457305908203s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0022039413452148438s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 7.939338684082031e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.239776611328125e-05s
INFO | --- Analysis for masc-bn-nif took 181.3713140487671s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 0.10789990425109863s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.4082932472229004s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.0280611515045166s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0010035037994384766s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 5.030632019042969e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 8.106231689453125e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 180.6312129497528s
Availability | SPARQL endpoint availability check for medline took 4.482269287109375e-05s
Availability | VoID file availability check for medline took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for medline took 60.2906231880188s
Reputation | Calculation of the PageRank for medline took 0.021048784255981445s
Interlinking | Calculation of Degree of Connection for medline took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for medline took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for medline took 4.267692565917969e-05s
Believability | Calculation of trust value for medline took 1.6689300537109375e-05s
INFO | --- Analysis for medline took 245.12107872962952s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 2.0760204792022705s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.32460737228393555s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02100968360900879s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.534027099609375e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.0967254638671875e-05s
INFO | --- Analysis for meducator took 368.1876528263092s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.172325134277344e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2906606197357178s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020900726318359375s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.9802322387695312e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 1.1920928955078125e-05s
INFO | --- Analysis for mesh-finnish took 1.7725188732147217s
Availability | SPARQL endpoint availability check for MeSH headings took 8.58306884765625e-05s
Availability | VoID file availability check for MeSH headings took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for MeSH headings took 60.02369737625122s
Reputation | Calculation of the PageRank for MeSH headings took 0.0215303897857666s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 4.0531158447265625e-05s
Believability | Calculation of trust value for MeSH headings took 1.1920928955078125e-05s
INFO | --- Analysis for mesh_headings took 240.69142937660217s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 8.535385131835938e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 180.1824221611023s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.021669387817382812s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 4.172325134277344e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 1.9311904907226562e-05s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 420.90035605430603s
Availability | SPARQL endpoint availability check for MeSH pairs took 8.368492126464844e-05s
Availability | VoID file availability check for MeSH pairs took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for MeSH pairs took 119.51522946357727s
Reputation | Calculation of the PageRank for MeSH pairs took 0.021076679229736328s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 3.7670135498046875e-05s
Believability | Calculation of trust value for MeSH pairs took 1.239776611328125e-05s
INFO | --- Analysis for mesh_pairs took 180.94279623031616s
Availability | SPARQL endpoint availability check for MeSH titles took 4.506111145019531e-05s
Availability | VoID file availability check for MeSH titles took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.3127586841583252s
Reputation | Calculation of the PageRank for MeSH titles took 0.02636408805847168s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0013194084167480469s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 4.410743713378906e-05s
Believability | Calculation of trust value for MeSH titles took 1.33514404296875e-05s
INFO | --- Analysis for mesh_titles took 240.57268571853638s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 8.606910705566406e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0007860660552978516s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.3009073734283447s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.021865129470825195s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0009970664978027344s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.5762786865234375e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 1.2874603271484375e-05s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 61.70109510421753s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.00010633468627929688s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0008263587951660156s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 60.21497869491577s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.025335311889648438s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0009860992431640625s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.000102996826171875s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.3113021850585938e-05s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 121.50048995018005s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 8.487701416015625e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.2900581359863281s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.024277210235595703s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0011110305786132812s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 8.845329284667969e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.239776611328125e-05s
INFO | --- Analysis for metashare took 1.859604835510254s
Availability | SPARQL endpoint availability check for MExiCo took 9.012222290039062e-05s
Availability | VoID file availability check for MExiCo took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for MExiCo took 59.85396718978882s
Reputation | Calculation of the PageRank for MExiCo took 0.025774717330932617s
Interlinking | Calculation of Degree of Connection for MExiCo took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0011944770812988281s
Interlinking | Calculation of Clustering coefficient for MExiCo took 7.200241088867188e-05s
Believability | Calculation of trust value for MExiCo took 1.2874603271484375e-05s
INFO | --- Analysis for mexico took 140.62058520317078s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.221334457397461s
Availability | VoID file availability check for Coronavirus dataset took 0.0007052421569824219s
Extra | Recovery of all triples for Coronavirus dataset took 5.8728392124176025s
Performance | Total latancy measurement for Coronavirus dataset took 2.9759838581085205s
Amount of data | Number of triples check for Coronavirus dataset took 0.8488643169403076s
Interoperability | New terms check for Coronavirus dataset took 2.2609474658966064s
Versatility | Languages check for Coronavirus dataset took 60.66772794723511s
Interpretability | Number of blank nodes check for Coronavirus dataset took 1.7435495853424072s
Interpretability | RDF structures check for Coronavirus dataset took 0.6467602252960205s
Versatility | Serialization formats check for Coronavirus dataset took 0.8173477649688721s
Availability | RDF dump link check for Coronavirus dataset took 0.7072865962982178s
License | MR license check for Coronavirus dataset took 1.3207600116729736s
License | HR license check for Coronavirus dataset took 27.16545844078064s
Amount of data | Number of property check for Coronavirus dataset took 0.6299669742584229s
Understandability | Number of label check for Coronavirus dataset took 2.259564161300659s
Understandability | URI regex check for Coronavirus dataset took 1.5077099800109863s
Understandability | Vocabs check for Coronavirus dataset took 0.6689105033874512s
Verifiability | Authors check for Coronavirus dataset took 0.897139310836792s
Verifiability | Publishers check for Coronavirus dataset took 0.7967028617858887s
Performance | Throughput check for Coronavirus dataset took 11.645808935165405s
Amount of data | Check the number of entities for Coronavirus dataset took 8.869171142578125e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.7097475528717041s
Interlinking | sameAs chians check for Coronavirus dataset took 0.7340054512023926s
Interlinking | skos check for Coronavirus dataset took 1.1547067165374756s
Interlinking | skos check for Coronavirus dataset took 0.5916955471038818s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.7300338745117188s
Currency | Creation date check for Coronavirus dataset took 0.7267670631408691s
Currency | Modification date check for Coronavirus dataset took 0.6114983558654785s
Rep.Conc. | URIs length for Coronavirus dataset took 5.7427167892456055s
Interoperability | New vocabularies check for Coronavirus dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.602947473526001s
Accuracy | Check Functional Property for Coronavirus dataset took 0.8703501224517822s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.845778226852417s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.343172788619995s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.023283004760742188s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.028711318969726562s
Consistency | Disjoint class check for Coronavirus dataset took 0.6008458137512207s
Consistency | Check Misplaced properties for Coronavirus dataset took 5.68536376953125s
Consistency | Misplaced classes for Coronavirus dataset took 0.7071752548217773s
Consistency | Check Ontology hijacking for Coronavirus dataset took 5.049358606338501s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.4873700141906738s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 4.5700600147247314s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.033704519271850586s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.6087996959686279s
Security | Sign check for Coronavirus dataset took 1.0209019184112549s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3455.0586183071136s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.7997045516967773s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021480798721313477s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.7642974853515625e-05s
INFO | --- Analysis for micro-coronavirus took 3965.495701313019s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00011992454528808594s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.31894993782043457s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02132725715637207s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010657310485839844s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.6689300537109375e-05s
INFO | --- Analysis for miguiadeviajes-gnoss took 65.00630831718445s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.654594421386719e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.3167908191680908s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02912449836730957s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0009143352508544922s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0001327991485595703s
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 61.999404430389404s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.00012063980102539062s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.31705164909362793s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.021129846572875977s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.982948303222656e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.059906005859375e-06s
INFO | --- Analysis for mlsa took 121.64747738838196s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 8.678436279296875e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 119.97077655792236s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.022069215774536133s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.528594970703125e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.8596649169921875e-05s
INFO | --- Analysis for model took 360.5294826030731s
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.00011754035949707031s
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.0005211830139160156s
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.3158257007598877s
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.03553128242492676s
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.5020370483398438e-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.0013461112976074219s
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 5.817413330078125e-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.6927719116210938e-05s
INFO | --- Analysis for model1 took 120.8443341255188s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 0.00012183189392089844s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.41962194442749023s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.021723508834838867s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0008592605590820312s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.314018249511719e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 2.956390380859375e-05s
INFO | --- Analysis for mond took 62.51353311538696s
Availability | SPARQL endpoint availability check for MONDIS took 8.392333984375e-05s
Availability | VoID file availability check for MONDIS took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for MONDIS took 0.3207862377166748s
Reputation | Calculation of the PageRank for MONDIS took 0.022816896438598633s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.001127481460571289s
Interlinking | Calculation of Clustering coefficient for MONDIS took 3.743171691894531e-05s
Believability | Calculation of trust value for MONDIS took 8.344650268554688e-06s
INFO | --- Analysis for mondis took 61.29207921028137s
Availability | SPARQL endpoint availability check for Monumentos took 8.606910705566406e-05s
Availability | VoID file availability check for Monumentos took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Monumentos took 0.3230001926422119s
Reputation | Calculation of the PageRank for Monumentos took 0.02191019058227539s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.075599670410156e-05s
Believability | Calculation of trust value for Monumentos took 1.3113021850585938e-05s
INFO | --- Analysis for monumentos-zaragoza took 61.94658041000366s
Availability | SPARQL endpoint availability check for MORElab took 8.749961853027344e-05s
Availability | VoID file availability check for MORElab took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for MORElab took 0.31813669204711914s
Reputation | Calculation of the PageRank for MORElab took 0.021163225173950195s
Interlinking | Calculation of Degree of Connection for MORElab took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for MORElab took 0.00011157989501953125s
Believability | Calculation of trust value for MORElab took 1.4543533325195312e-05s
INFO | --- Analysis for morelab took 301.14823842048645s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 8.535385131835938e-05s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.37865281105041504s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.048564910888671875s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0023605823516845703s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 0.00022673606872558594s
Believability | Calculation of trust value for Mathematics Subject Classification took 9.298324584960938e-06s
INFO | --- Analysis for msc took 61.72610831260681s
Availability | SPARQL endpoint availability check for Multext-East took 0.00010013580322265625s
Availability | VoID file availability check for Multext-East took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Multext-East took 0.31696033477783203s
Reputation | Calculation of the PageRank for Multext-East took 0.02706432342529297s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0011966228485107422s
Interlinking | Calculation of Clustering coefficient for Multext-East took 4.267692565917969e-05s
Believability | Calculation of trust value for Multext-East took 1.9550323486328125e-05s
INFO | --- Analysis for multext-east took 121.97317719459534s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.655952453613281e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0003705024719238281s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.3228263854980469s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.02159595489501953s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.0994415283203125e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.0251998901367188e-05s
INFO | --- Analysis for multilingualeulaw took 62.25279450416565s
Availability | SPARQL endpoint availability check for Multimedia Lab took 9.584426879882812e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0008063316345214844s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.3293149471282959s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.022791385650634766s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0013911724090576172s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 6.008148193359375e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.239776611328125e-05s
INFO | --- Analysis for multimedia-lab took 361.37580847740173s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 8.749961853027344e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.3202531337738037s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.552436828613281e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 7.867813110351562e-06s
INFO | --- Analysis for munich-offener-haushalt took 61.72859525680542s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.9107584953308105s
Availability | VoID file availability check for Muninn World War I took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Muninn World War I took 59.952985525131226s
Reputation | Calculation of the PageRank for Muninn World War I took 0.028562545776367188s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0013315677642822266s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 0.00011920928955078125s
Believability | Calculation of trust value for Muninn World War I took 1.2159347534179688e-05s
INFO | --- Analysis for muninn-world-war-i took 68.30157446861267s
Availability | SPARQL endpoint availability check for Musei Italiani took 8.058547973632812e-05s
Availability | VoID file availability check for Musei Italiani took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.37398600578308105s
Reputation | Calculation of the PageRank for Musei Italiani took 0.023426055908203125s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0011157989501953125s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 4.673004150390625e-05s
Believability | Calculation of trust value for Musei Italiani took 1.2874603271484375e-05s
INFO | --- Analysis for musei-italiani took 61.22644400596619s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011134147644042969s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 120.34913969039917s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0213315486907959s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00012755393981933594s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0728836059570312e-05s
INFO | --- Analysis for museosespania-gnoss took 426.51348638534546s
Availability | SPARQL endpoint availability check for Italian Museums took 1.4252724647521973s
Availability | VoID file availability check for Italian Museums took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.3323483467102051s
Reputation | Calculation of the PageRank for Italian Museums took 0.023012876510620117s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0010597705841064453s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 0.00011157989501953125s
Believability | Calculation of trust value for Italian Museums took 1.2159347534179688e-05s
INFO | --- Analysis for museums-in-italy took 63.35761594772339s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.38690185546875e-05s
Availability | VoID file availability check for MusicBrainz took 0.0008480548858642578s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.36772704124450684s
Reputation | Calculation of the PageRank for MusicBrainz took 0.03345036506652832s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0015780925750732422s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 5.459785461425781e-05s
Believability | Calculation of trust value for MusicBrainz took 1.049041748046875e-05s
INFO | --- Analysis for musicbrainz_ took 121.0202910900116s
Availability | SPARQL endpoint availability check for MusicNet Codex took 9.560585021972656e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.3519718647003174s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.024793386459350586s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 3.0517578125e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.001279592514038086s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 5.6743621826171875e-05s
Believability | Calculation of trust value for MusicNet Codex took 1.3113021850585938e-05s
INFO | --- Analysis for musicnet_codex took 61.50454902648926s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7648329734802246s
Availability | VoID file availability check for Muziekweb took 0.0003352165222167969s
Extra | Recovery of all triples for Muziekweb took 1.4221770763397217s
Performance | Total latancy measurement for Muziekweb took 1.5020620822906494s
Amount of data | Number of triples check for Muziekweb took 0.3807253837585449s
Interoperability | New terms check for Muziekweb took 1.955526351928711s
Versatility | Languages check for Muziekweb took 46.366673707962036s
Interpretability | Number of blank nodes check for Muziekweb took 0.31637001037597656s
Interpretability | RDF structures check for Muziekweb took 0.33471250534057617s
Versatility | Serialization formats check for Muziekweb took 0.29788994789123535s
Availability | RDF dump link check for Muziekweb took 0.3278181552886963s
License | MR license check for Muziekweb took 0.311629056930542s
License | HR license check for Muziekweb took 11.442344188690186s
Amount of data | Number of property check for Muziekweb took 0.33432888984680176s
Understandability | Number of label check for Muziekweb took 0.3691868782043457s
Understandability | URI regex check for Muziekweb took 0.6183364391326904s
Understandability | Vocabs check for Muziekweb took 0.3087782859802246s
Verifiability | Authors check for Muziekweb took 0.3091928958892822s
Verifiability | Publishers check for Muziekweb took 0.28387880325317383s
Performance | Throughput check for Muziekweb took 11.812014818191528s
Amount of data | Check the number of entities for Muziekweb took 0.0001289844512939453s
Verifiability | Contribs. check for Muziekweb took 0.31340622901916504s
Interlinking | sameAs chians check for Muziekweb took 0.3161592483520508s
Interlinking | skos check for Muziekweb took 0.30265283584594727s
Interlinking | skos check for Muziekweb took 0.28921055793762207s
Timeliness | dataset update frequency check for Muziekweb took 0.31354832649230957s
Currency | Creation date check for Muziekweb took 0.8308532238006592s
Currency | Modification date check for Muziekweb took 0.8438611030578613s
Rep.Conc. | URIs length for Muziekweb took 1.7375199794769287s
Interoperability | New vocabularies check for Muziekweb took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.303286075592041s
Accuracy | Check Functional Property for Muziekweb took 0.526862382888794s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5294680595397949s
Accuracy | Check Empty annotation labels for Muziekweb took 2.4355690479278564s
Accuracy | Check White space in annotation for Muziekweb took 0.028282642364501953s
Accuracy | Check Datatype consistency for Muziekweb took 0.029389619827270508s
Consistency | Disjoint class check for Muziekweb took 0.5667953491210938s
Consistency | Check Misplaced properties for Muziekweb took 0.6034896373748779s
Consistency | Check Ontology hijacking for Muziekweb took 2.2201058864593506s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.4249017238616943s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.661921501159668s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03426361083984375s
Conciseness | Check Intensional conciseness for Muziekweb took 0.30201220512390137s
Security | Sign check for Muziekweb took 0.28092074394226074s
Availability | Check URIs Dereferenciability for Muziekweb took 1810.7687594890594s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.7304036617279053s
Reputation | Calculation of the PageRank for Muziekweb took 0.022677898406982422s
Interlinking | Calculation of Degree of Connection for Muziekweb took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0014567375183105469s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 0.00013709068298339844s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 2.6226043701171875e-06s
Believability | Calculation of trust value for Muziekweb took 1.5974044799804688e-05s
INFO | --- Analysis for muziekweb took 2167.9057030677795s
Availability | SPARQL endpoint availability check for myExperiment took 0.4469478130340576s
Availability | VoID file availability check for myExperiment took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for myExperiment took 0.29712796211242676s
Reputation | Calculation of the PageRank for myExperiment took 0.029535293579101562s
Interlinking | Calculation of Degree of Connection for myExperiment took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.002337932586669922s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.0003304481506347656s
Believability | Calculation of trust value for myExperiment took 1.3113021850585938e-05s
INFO | --- Analysis for my-experiment took 63.33664608001709s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.08929610252380371s
Availability | VoID file availability check for My Family Lineage took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for My Family Lineage took 59.965516328811646s
Reputation | Calculation of the PageRank for My Family Lineage took 0.023175477981567383s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0008397102355957031s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 9.489059448242188e-05s
Believability | Calculation of trust value for My Family Lineage took 1.2159347534179688e-05s
INFO | --- Analysis for my-family-lineage took 121.76370453834534s
Availability | SPARQL endpoint availability check for My ontology test took 1.1262874603271484s
Availability | VoID file availability check for My ontology test took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for My ontology test took 119.60406613349915s
Reputation | Calculation of the PageRank for My ontology test took 0.02240729331970215s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0008859634399414062s
Interlinking | Calculation of Clustering coefficient for My ontology test took 4.6253204345703125e-05s
Believability | Calculation of trust value for My ontology test took 1.2159347534179688e-05s
INFO | --- Analysis for myontologytest took 541.4992849826813s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 9.298324584960938e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0009257793426513672s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 179.6813862323761s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.025307178497314453s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0012323856353759766s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.0001513957977294922s
Believability | Calculation of trust value for myopenlink dataspaces took 1.33514404296875e-05s
INFO | --- Analysis for myopenlink-dataspaces took 253.27579975128174s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 2.317436933517456s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 119.9008104801178s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.027005672454833984s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0013387203216552734s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 0.00011181831359863281s
Believability | Calculation of trust value for N-Lex as Linked Data took 7.62939453125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 188.58719396591187s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.053044319152832s
Availability | VoID file availability check for NAICS 2007 took 0.0009496212005615234s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.4164609909057617s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02191329002380371s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0013194084167480469s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 7.2479248046875e-05s
Believability | Calculation of trust value for NAICS 2007 took 1.2874603271484375e-05s
INFO | --- Analysis for naics-2007 took 266.64222717285156s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.50626277923584s
Availability | VoID file availability check for NAICS 2012 took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.5181756019592285s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.029050588607788086s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.001421213150024414s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 8.249282836914062e-05s
Believability | Calculation of trust value for NAICS 2012 took 1.3113021850585938e-05s
INFO | --- Analysis for naics-2012 took 146.47983956336975s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 8.749961853027344e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 59.99328827857971s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.022579431533813477s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0009059906005859375s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 8.606910705566406e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for nalt took 300.9646999835968s
Availability | SPARQL endpoint availability check for Usernames  took 9.226799011230469e-05s
Availability | VoID file availability check for Usernames  took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Usernames  took 59.7182080745697s
Reputation | Calculation of the PageRank for Usernames  took 0.02243328094482422s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0011992454528808594s
Interlinking | Calculation of Clustering coefficient for Usernames  took 4.3392181396484375e-05s
Believability | Calculation of trust value for Usernames  took 1.3828277587890625e-05s
INFO | --- Analysis for Names took 61.280548334121704s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 0.8987233638763428s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007348060607910156s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.3423848152160645s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 4.11285662651062s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 11.412361860275269s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 14.869311809539795s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.765716552734375s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.545570373535156s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.7573666572570801s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.7847902774810791s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.7685670852661133s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.7693130970001221s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3184316158294678s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 92.18890857696533s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8273189067840576s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 5.193251609802246s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 1.5472702980041504s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.3248178958892822s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.7859494686126709s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.7889018058776855s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 15.20038104057312s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.988380432128906e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.7665870189666748s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.8537440299987793s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.7284636497497559s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.697657823562622s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.7762506008148193s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 13.429291009902954s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 19.241419315338135s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.1224303245544434s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.8058607578277588s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.31925201416015625s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.32097411155700684s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.3497927188873291s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007631778717041016s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010905265808105469s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.7737340927124023s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 1.5472354888916016s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.7763574123382568s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.8742115497589111s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.4562621116638184s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 2.301414966583252s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006375312805175781s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3253793716430664s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 7.265205383300781s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.3583672046661377s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02260446548461914s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0010685920715332031s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 2.6226043701171875e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 1.2636184692382812e-05s
INFO | --- Analysis for national-diet-library-authorities took 560.603245973587s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.7928164005279541s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0012352466583251953s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.546825885772705s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 3.63405704498291s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.721444845199585s
Interoperability | New terms check for National Diet Library of Japan subject headings took 14.487438678741455s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.8173456192016602s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.467500686645508s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.7494308948516846s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.7716138362884521s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.7783446311950684s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.771935224533081s
License | MR license check for National Diet Library of Japan subject headings took 0.7820844650268555s
License | HR license check for National Diet Library of Japan subject headings took 92.22605299949646s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8098328113555908s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.304928541183472s
Understandability | URI regex check for National Diet Library of Japan subject headings took 1.555877685546875s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.7819998264312744s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.7745804786682129s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.7885820865631104s
Performance | Throughput check for National Diet Library of Japan subject headings took 15.044208526611328s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.678436279296875e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.7737553119659424s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.8596599102020264s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.7666680812835693s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.7123327255249023s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.8942797183990479s
Currency | Creation date check for National Diet Library of Japan subject headings took 10.002765417098999s
Currency | Modification date check for National Diet Library of Japan subject headings took 18.190823316574097s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 1.788731336593628s
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.7921750545501709s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.7736649513244629s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.7772607803344727s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.7859599590301514s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007708072662353516s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0011305809020996094s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.7939193248748779s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 1.5526835918426514s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.7791798114776611s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.8093488216400146s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.4433729648590088s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 2.145023822784424s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006885528564453125s
Security | Sign check for National Diet Library of Japan subject headings took 0.778846025466919s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 6.33348274230957s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 120.08262276649475s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.021277666091918945s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.9073486328125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.3828277587890625e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 561.3260188102722s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.9427855014801025s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0007822513580322266s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 120.26132249832153s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.0236666202545166s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.863739013671875e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 9.5367431640625e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 123.63463640213013s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00010538101196289062s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.3097958564758301s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.021317005157470703s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.128715515136719e-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 2.713322401046753s
Availability | SPARQL endpoint availability check for Naturopathy took 0.00010514259338378906s
Availability | VoID file availability check for Naturopathy took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for Naturopathy took 59.63332414627075s
Reputation | Calculation of the PageRank for Naturopathy took 0.02500319480895996s
Interlinking | Calculation of Degree of Connection for Naturopathy took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0012891292572021484s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 7.700920104980469e-05s
Believability | Calculation of trust value for Naturopathy took 1.3828277587890625e-05s
INFO | --- Analysis for naturopathy2 took 359.97545862197876s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 0.00010824203491210938s
Availability | VoID file availability check for NCI Thesaurus took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 60.3822603225708s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02112722396850586s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.3855438232421875e-05s
Believability | Calculation of trust value for NCI Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for nci-thesaurus took 181.28122520446777s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.9348843097686768s
Availability | VoID file availability check for COVID-19 Data took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.4024972915649414s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.022866010665893555s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 2.956390380859375e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.3113021850585938e-05s
INFO | --- Analysis for NCMI-COVID-19 took 364.7641134262085s
Availability | SPARQL endpoint availability check for NDF-RT took 8.511543273925781e-05s
Availability | VoID file availability check for NDF-RT took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.2892460823059082s
Reputation | Calculation of the PageRank for NDF-RT took 0.023146867752075195s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.266334533691406e-05s
Believability | Calculation of trust value for NDF-RT took 1.6450881958007812e-05s
INFO | --- Analysis for ndf-rt took 120.76941442489624s
Availability | SPARQL endpoint availability check for Near took 0.00013017654418945312s
Availability | VoID file availability check for Near took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for Near took 0.3074314594268799s
Reputation | Calculation of the PageRank for Near took 0.021409034729003906s
Interlinking | Calculation of Degree of Connection for Near took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Near took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Near took 9.72747802734375e-05s
Believability | Calculation of trust value for Near took 1.1444091796875e-05s
INFO | --- Analysis for near took 67.0008134841919s
Availability | SPARQL endpoint availability check for Neel took 8.511543273925781e-05s
Availability | VoID file availability check for Neel took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Neel took 0.3189396858215332s
Reputation | Calculation of the PageRank for Neel took 0.021986961364746094s
Interlinking | Calculation of Degree of Connection for Neel took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Neel took 0.000823974609375s
Interlinking | Calculation of Clustering coefficient for Neel took 3.337860107421875e-05s
Believability | Calculation of trust value for Neel took 1.3113021850585938e-05s
INFO | --- Analysis for neel took 1.7063701152801514s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 8.821487426757812e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.3417651653289795s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.02249908447265625s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0010869503021240234s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.886222839355469e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 1.2159347534179688e-05s
INFO | --- Analysis for neurocommons_text_mining_pilot took 61.720324754714966s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 9.131431579589844e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.41760921478271484s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.021268129348754883s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.552436828613281e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.1444091796875e-05s
INFO | --- Analysis for neurolex-wiki took 121.25891089439392s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 8.893013000488281e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.3453366756439209s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.021903514862060547s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0008420944213867188s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 5.53131103515625e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.2636184692382812e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 301.7970416545868s
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.0015511512756347656s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.35817670822143555s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020983457565307617s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.723403930664062e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.1444091796875e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 3.5124003887176514s
Availability | SPARQL endpoint availability check for Newsweek took 4.5299530029296875e-05s
Availability | VoID file availability check for Newsweek took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for Newsweek took 0.3997056484222412s
Reputation | Calculation of the PageRank for Newsweek took 0.0220949649810791s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0008676052093505859s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.8623809814453125e-05s
Believability | Calculation of trust value for Newsweek took 1.1920928955078125e-05s
INFO | --- Analysis for newsweek took 121.21697783470154s
Availability | SPARQL endpoint availability check for neXtProt took 0.39728426933288574s
Availability | VoID file availability check for neXtProt took 0.0005311965942382812s
Extra | Recovery of all triples for neXtProt took 7.356111288070679s
Performance | Total latancy measurement for neXtProt took 0.441389799118042s
Amount of data | Number of triples check for neXtProt took 0.08758544921875s
Interoperability | New terms check for neXtProt took 1.5350534915924072s
Versatility | Languages check for neXtProt took 0.08709836006164551s
Interpretability | Number of blank nodes check for neXtProt took 0.0870199203491211s
Interpretability | RDF structures check for neXtProt took 0.0871269702911377s
Versatility | Serialization formats check for neXtProt took 0.07565474510192871s
Availability | RDF dump link check for neXtProt took 0.08666777610778809s
License | MR license check for neXtProt took 0.08709049224853516s
License | HR license check for neXtProt took 0.08683109283447266s
Amount of data | Number of property check for neXtProt took 0.10206341743469238s
Understandability | Number of label check for neXtProt took 0.08726382255554199s
Understandability | URI regex check for neXtProt took 0.16358447074890137s
Understandability | Vocabs check for neXtProt took 0.09781265258789062s
Verifiability | Authors check for neXtProt took 0.08754372596740723s
Verifiability | Publishers check for neXtProt took 0.07616543769836426s
Performance | Throughput check for neXtProt took 10.559906959533691s
Amount of data | Check the number of entities for neXtProt took 4.6253204345703125e-05s
Verifiability | Contribs. check for neXtProt took 0.08755850791931152s
Interlinking | sameAs chians check for neXtProt took 0.08750176429748535s
Interlinking | skos check for neXtProt took 0.08797168731689453s
Interlinking | skos check for neXtProt took 0.07690644264221191s
Timeliness | dataset update frequency check for neXtProt took 0.0770876407623291s
Currency | Creation date check for neXtProt took 0.08795022964477539s
Currency | Modification date check for neXtProt took 0.09300708770751953s
Rep.Conc. | URIs length for neXtProt took 14.174383163452148s
Interoperability | New vocabularies check for neXtProt took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for neXtProt took 0.08623051643371582s
Accuracy | Check Functional Property for neXtProt took 0.07332301139831543s
Accuracy | Check Inverse Functional Property for neXtProt took 0.09555172920227051s
Accuracy | Check Empty annotation labels for neXtProt took 7.923901081085205s
Accuracy | Check White space in annotation for neXtProt took 3.0156362056732178s
Accuracy | Check Datatype consistency for neXtProt took 2.658676862716675s
Consistency | Disjoint class check for neXtProt took 0.08811402320861816s
Consistency | Check Misplaced properties for neXtProt took 0.21410441398620605s
Consistency | Misplaced classes for neXtProt took 8.367680311203003s
Consistency | Check Ontology hijacking for neXtProt took 6.506340742111206s
Consistency | Check Invalid usage of undefined classes for neXtProt took 1.4520065784454346s
Consistency | Check Invalid usage of undefined properties for neXtProt took 1.5559844970703125s
Conciseness | Check Extensional conciseness for neXtProt took 2.9888083934783936s
Conciseness | Check Intensional conciseness for neXtProt took 0.12021112442016602s
Security | Sign check for neXtProt took 0.07643580436706543s
Availability | Check URIs Dereferenciability for neXtProt took 1907.0056555271149s
Completeness | Calculation of interlinking completeness for neXtProt took 0.6260216236114502s
Reputation | Calculation of the PageRank for neXtProt took 0.021490812301635742s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for neXtProt took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for neXtProt took 1.6689300537109375e-06s
Believability | Calculation of trust value for neXtProt took 7.3909759521484375e-06s
INFO | --- Analysis for nextprot took 2064.3005204200745s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010800361633300781s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.31944799423217773s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.022612333297729492s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0012805461883544922s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0001418590545654297s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for nextweb-gnoss took 187.02651834487915s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 9.059906005859375e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 60.38352084159851s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.022542476654052734s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0010590553283691406s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 0.00010251998901367188s
Believability | Calculation of trust value for NHS Jargon RDF took 7.3909759521484375e-06s
INFO | --- Analysis for nhs-jargon took 121.9526309967041s
Availability | SPARQL endpoint availability check for NIT Patna took 9.72747802734375e-05s
Availability | VoID file availability check for NIT Patna took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.33144092559814453s
Reputation | Calculation of the PageRank for NIT Patna took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for NIT Patna took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 8.749961853027344e-05s
Believability | Calculation of trust value for NIT Patna took 1.811981201171875e-05s
INFO | --- Analysis for NITP took 122.73973560333252s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 0.00010728836059570312s
Availability | VoID file availability check for NLM 2007 MeSH took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.35787153244018555s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.02550792694091797s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0012278556823730469s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 8.106231689453125e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 1.2159347534179688e-05s
INFO | --- Analysis for nlm_2007_mesh took 539.6891026496887s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 9.107589721679688e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.000743865966796875s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2986478805541992s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02388453483581543s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0011239051818847656s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 4.6253204345703125e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.7404556274414062e-05s
INFO | --- Analysis for nlr-dataset-mod took 243.13116335868835s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6157443523406982s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.29815006256103516s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.02489495277404785s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.001277923583984375s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 6.890296936035156e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for NLW took 182.8569815158844s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.0602457523345947s
Availability | VoID file availability check for Nobel Prizes took 0.0008385181427001953s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 60.32759881019592s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.027260541915893555s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0014231204986572266s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 0.00017118453979492188s
Believability | Calculation of trust value for Nobel Prizes took 1.3828277587890625e-05s
INFO | --- Analysis for nobelprizes took 66.88959240913391s
Availability | SPARQL endpoint availability check for NoiPA took 0.20972132682800293s
Availability | VoID file availability check for NoiPA took 0.0005216598510742188s
Extra | Recovery of all triples for NoiPA took 1.1685471534729004s
Performance | Total latancy measurement for NoiPA took 0.36762571334838867s
Amount of data | Number of triples check for NoiPA took 1.2571518421173096s
Interoperability | New terms check for NoiPA took 2.7671947479248047s
Versatility | Languages check for NoiPA took 60.11279797554016s
Interpretability | Number of blank nodes check for NoiPA took 0.7466621398925781s
Interpretability | RDF structures check for NoiPA took 0.5295288562774658s
Versatility | Serialization formats check for NoiPA took 0.14888978004455566s
Availability | RDF dump link check for NoiPA took 0.13720488548278809s
License | MR license check for NoiPA took 0.1583251953125s
License | HR license check for NoiPA took 60.18232750892639s
Amount of data | Number of property check for NoiPA took 0.12400579452514648s
Understandability | Number of label check for NoiPA took 0.5643837451934814s
Understandability | URI regex check for NoiPA took 0.2546210289001465s
Understandability | Vocabs check for NoiPA took 0.07747578620910645s
Verifiability | Authors check for NoiPA took 0.08131241798400879s
Verifiability | Publishers check for NoiPA took 0.0778813362121582s
Performance | Throughput check for NoiPA took 10.500200986862183s
Amount of data | Check the number of entities for NoiPA took 9.632110595703125e-05s
Verifiability | Contribs. check for NoiPA took 0.114044189453125s
Interlinking | sameAs chians check for NoiPA took 0.12012004852294922s
Interlinking | skos check for NoiPA took 0.3695404529571533s
Interlinking | skos check for NoiPA took 0.06685543060302734s
Timeliness | dataset update frequency check for NoiPA took 0.11725187301635742s
Currency | Creation date check for NoiPA took 0.12066817283630371s
Currency | Modification date check for NoiPA took 0.1129004955291748s
Rep.Conc. | URIs length for NoiPA took 16.103874444961548s
Interoperability | New vocabularies check for NoiPA took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.07538986206054688s
Accuracy | Check Functional Property for NoiPA took 0.16471409797668457s
Accuracy | Check Inverse Functional Property for NoiPA took 0.08209085464477539s
Accuracy | Check Empty annotation labels for NoiPA took 0.3848247528076172s
Accuracy | Check White space in annotation for NoiPA took 0.031008481979370117s
Accuracy | Check Datatype consistency for NoiPA took 0.031232118606567383s
Consistency | Disjoint class check for NoiPA took 0.10499095916748047s
Consistency | Check Misplaced properties for NoiPA took 14.670703649520874s
Consistency | Misplaced classes for NoiPA took 0.17023539543151855s
Consistency | Check Ontology hijacking for NoiPA took 1.9684069156646729s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.4492859840393066s
Consistency | Check Invalid usage of undefined properties for NoiPA took 16.31526207923889s
Conciseness | Check Extensional conciseness for NoiPA took 0.038645267486572266s
Conciseness | Check Intensional conciseness for NoiPA took 0.15577363967895508s
Security | Sign check for NoiPA took 0.10369229316711426s
Availability | Check URIs Dereferenciability for NoiPA took 11.959421157836914s
Completeness | Calculation of interlinking completeness for NoiPA took 60.62111234664917s
Reputation | Calculation of the PageRank for NoiPA took 0.02297687530517578s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0010242462158203125s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.9073486328125e-06s
Believability | Calculation of trust value for NoiPA took 1.0967254638671875e-05s
INFO | --- Analysis for NoiPA took 709.4111423492432s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.022963523864746s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.00040221214294433594s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 60.19555974006653s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.021259307861328125s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.679794311523438e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.3113021850585938e-05s
INFO | --- Analysis for nom took 425.8431646823883s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 25.243632793426514s
Availability | VoID file availability check for Nomenclator Asturias took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 180.18022227287292s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.029892444610595703s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0011968612670898438s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 0.00011491775512695312s
Believability | Calculation of trust value for Nomenclator Asturias took 1.621246337890625e-05s
INFO | --- Analysis for nomenclator-asturias took 583.7252035140991s
Availability | SPARQL endpoint availability check for nomisma took 9.036064147949219e-05s
Availability | VoID file availability check for nomisma took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for nomisma took 0.29806995391845703s
Reputation | Calculation of the PageRank for nomisma took 0.024011850357055664s
Interlinking | Calculation of Degree of Connection for nomisma took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0008716583251953125s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.7670135498046875e-05s
Believability | Calculation of trust value for nomisma took 1.3828277587890625e-05s
INFO | --- Analysis for nomisma took 121.85410594940186s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.3724043369293213s
Availability | VoID file availability check for Nomisma.org  took 0.0006835460662841797s
Extra | Recovery of all triples for Nomisma.org  took 82.00210189819336s
Performance | Total latancy measurement for Nomisma.org  took 1.3239917755126953s
Amount of data | Number of triples check for Nomisma.org  took 36.22556924819946s
Interoperability | New terms check for Nomisma.org  took 8.465806007385254s
Versatility | Languages check for Nomisma.org  took 83.3226466178894s
Interpretability | Number of blank nodes check for Nomisma.org  took 25.638748168945312s
Security | Check HTTPS for Nomisma.org  took 0.6135637760162354s
Interpretability | RDF structures check for Nomisma.org  took 0.2968332767486572s
Versatility | Serialization formats check for Nomisma.org  took 0.4046337604522705s
Availability | RDF dump link check for Nomisma.org  took 1069.1477007865906s
License | MR license check for Nomisma.org  took 0.29492759704589844s
License | HR license check for Nomisma.org  took 54.004881143569946s
Amount of data | Number of property check for Nomisma.org  took 0.29730868339538574s
Understandability | Number of label check for Nomisma.org  took 6.108564376831055s
Understandability | URI regex check for Nomisma.org  took 0.5216593742370605s
Understandability | Vocabs check for Nomisma.org  took 0.24216580390930176s
Verifiability | Authors check for Nomisma.org  took 0.29048585891723633s
Verifiability | Publishers check for Nomisma.org  took 0.31655049324035645s
Performance | Throughput check for Nomisma.org  took 10.423235177993774s
Amount of data | Check the number of entities for Nomisma.org  took 60.70401120185852s
Verifiability | Contribs. check for Nomisma.org  took 0.2897372245788574s
Interlinking | sameAs chians check for Nomisma.org  took 0.2696709632873535s
Interlinking | skos check for Nomisma.org  took 1.5563430786132812s
Interlinking | skos check for Nomisma.org  took 0.4434671401977539s
Timeliness | dataset update frequency check for Nomisma.org  took 0.2711918354034424s
Currency | Creation date check for Nomisma.org  took 0.2945435047149658s
Currency | Modification date check for Nomisma.org  took 0.5366001129150391s
Rep.Conc. | URIs length for Nomisma.org  took 73.75496768951416s
Interoperability | New vocabularies check for Nomisma.org  took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.2781703472137451s
Accuracy | Check Functional Property for Nomisma.org  took 0.2906327247619629s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.26212024688720703s
Accuracy | Check Empty annotation labels for Nomisma.org  took 26.09971261024475s
Accuracy | Check White space in annotation for Nomisma.org  took 2.7129099369049072s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.602696418762207s
Consistency | Disjoint class check for Nomisma.org  took 0.2731165885925293s
Consistency | Check Misplaced properties for Nomisma.org  took 25.136608362197876s
Consistency | Check Ontology hijacking for Nomisma.org  took 28.18594002723694s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 2.273953437805176s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 26.52994394302368s
Conciseness | Check Extensional conciseness for Nomisma.org  took 3.192976713180542s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.2953956127166748s
Security | Sign check for Nomisma.org  took 0.24983668327331543s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1620.4967024326324s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.7077507972717285s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.9772450923919678s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.9073486328125e-06s
Believability | Calculation of trust value for Nomisma.org  took 8.821487426757812e-06s
INFO | --- Analysis for nomisma_org took 6561.5313901901245s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.3339674472808838s
Availability | VoID file availability check for Curriculum Vitae took 0.0004394054412841797s
Extra | Recovery of all triples for Curriculum Vitae took 0.5594704151153564s
Performance | Total latancy measurement for Curriculum Vitae took 1.6218078136444092s
Amount of data | Number of triples check for Curriculum Vitae took 0.2508656978607178s
Interoperability | New terms check for Curriculum Vitae took 1.7800791263580322s
Versatility | Languages check for Curriculum Vitae took 0.14969635009765625s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.14796233177185059s
Interpretability | RDF structures check for Curriculum Vitae took 0.13746070861816406s
Versatility | Serialization formats check for Curriculum Vitae took 0.13120388984680176s
Availability | RDF dump link check for Curriculum Vitae took 0.13421964645385742s
License | MR license check for Curriculum Vitae took 0.13399744033813477s
License | HR license check for Curriculum Vitae took 0.14145898818969727s
Amount of data | Number of property check for Curriculum Vitae took 0.24762868881225586s
Understandability | Number of label check for Curriculum Vitae took 0.2695786952972412s
Understandability | URI regex check for Curriculum Vitae took 0.48983240127563477s
Understandability | Vocabs check for Curriculum Vitae took 0.1300346851348877s
Verifiability | Authors check for Curriculum Vitae took 0.3894052505493164s
Verifiability | Publishers check for Curriculum Vitae took 0.22325825691223145s
Performance | Throughput check for Curriculum Vitae took 10.64798378944397s
Amount of data | Check the number of entities for Curriculum Vitae took 8.463859558105469e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.2567453384399414s
Interlinking | sameAs chians check for Curriculum Vitae took 0.12794256210327148s
Interlinking | skos check for Curriculum Vitae took 0.12811493873596191s
Interlinking | skos check for Curriculum Vitae took 0.12867355346679688s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.12353825569152832s
Currency | Creation date check for Curriculum Vitae took 0.24220490455627441s
Currency | Modification date check for Curriculum Vitae took 0.24745464324951172s
Rep.Conc. | URIs length for Curriculum Vitae took 0.3320188522338867s
Interoperability | New vocabularies check for Curriculum Vitae took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.10977911949157715s
Accuracy | Check Functional Property for Curriculum Vitae took 0.13244414329528809s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.13756537437438965s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.14975690841674805s
Accuracy | Check White space in annotation for Curriculum Vitae took 5.2928924560546875e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0018587112426757812s
Consistency | Disjoint class check for Curriculum Vitae took 0.14257454872131348s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.2559220790863037s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.8479993343353271s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.6887214183807373s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.8057198524475098s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0016431808471679688s
Security | Sign check for Curriculum Vitae took 0.2266862392425537s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.33728528022766s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.2857644557952881s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.0224306583404541s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0008487701416015625s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.9073486328125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.239776611328125e-05s
INFO | --- Analysis for Nordine_Bittich took 178.5156810283661s
Availability | SPARQL endpoint availability check for NorPark took 0.17924118041992188s
Availability | VoID file availability check for NorPark took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for NorPark took 0.2739837169647217s
Reputation | Calculation of the PageRank for NorPark took 0.029865026473999023s
Interlinking | Calculation of Degree of Connection for NorPark took 5.1975250244140625e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0027511119842529297s
Interlinking | Calculation of Clustering coefficient for NorPark took 0.00042247772216796875s
Believability | Calculation of trust value for NorPark took 1.4066696166992188e-05s
INFO | --- Analysis for norpark took 2.1712653636932373s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.016153812408447266s
Availability | VoID file availability check for Parking Dataset took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.3651440143585205s
Reputation | Calculation of the PageRank for Parking Dataset took 0.028184175491333008s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0015316009521484375s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 8.249282836914062e-05s
Believability | Calculation of trust value for Parking Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for norpark2 took 181.93585300445557s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.6508927345275879s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0007245540618896484s
Extra | Recovery of all triples for Norway fishery stocks dataset took 104.16477513313293s
Performance | Total latancy measurement for Norway fishery stocks dataset took 1.0005884170532227s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.72034478187561s
Interoperability | New terms check for Norway fishery stocks dataset took 14.49789834022522s
Versatility | Languages check for Norway fishery stocks dataset took 300.21685695648193s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 1.9038140773773193s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.2644367218017578s
Versatility | Serialization formats check for Norway fishery stocks dataset took 0.5674242973327637s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.29529666900634766s
License | MR license check for Norway fishery stocks dataset took 0.6867358684539795s
License | HR license check for Norway fishery stocks dataset took 300.18506050109863s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.22079968452453613s
Understandability | Number of label check for Norway fishery stocks dataset took 2.447859525680542s
Understandability | URI regex check for Norway fishery stocks dataset took 1.098745584487915s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.5101888179779053s
Verifiability | Authors check for Norway fishery stocks dataset took 0.21529626846313477s
Verifiability | Publishers check for Norway fishery stocks dataset took 2.9426684379577637s
Performance | Throughput check for Norway fishery stocks dataset took 11.221713304519653s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 8.630752563476562e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.19253849983215332s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.19626832008361816s
Interlinking | skos check for Norway fishery stocks dataset took 0.42129993438720703s
Interlinking | skos check for Norway fishery stocks dataset took 0.44055891036987305s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 0.7790708541870117s
Currency | Creation date check for Norway fishery stocks dataset took 1.1353087425231934s
Currency | Modification date check for Norway fishery stocks dataset took 0.25421977043151855s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 153.718332529068s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.2103426456451416s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.37582945823669434s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.4799532890319824s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 35.478407859802246s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.735351800918579s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.8520801067352295s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.19389057159423828s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 85.4274160861969s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.420730113983154s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 29.892688751220703s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.45912766456604s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 87.1715784072876s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 3.244291305541992s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.49071788787841797s
Security | Sign check for Norway fishery stocks dataset took 1.4264249801635742s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 21.687307596206665s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.5563483238220215s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.02144765853881836s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 2.384185791015625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.4781951904296875e-05s
INFO | --- Analysis for Norway_Fishery_ took 2304.6463766098022s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.5854151248931885s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.281757116317749s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.022926807403564453s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 6.341934204101562e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.4543533325195312e-05s
INFO | --- Analysis for norwegian-geo-divisions took 303.2814292907715s
Availability | SPARQL endpoint availability check for NorwegianSoE took 9.036064147949219e-05s
Availability | VoID file availability check for NorwegianSoE took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 59.89664626121521s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.02615833282470703s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0015883445739746094s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 6.556510925292969e-05s
Believability | Calculation of trust value for NorwegianSoE took 1.2636184692382812e-05s
INFO | --- Analysis for norwegiansoe took 180.9321928024292s
Availability | SPARQL endpoint availability check for NITP took 0.00011467933654785156s
Availability | VoID file availability check for NITP took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for NITP took 0.3170783519744873s
Reputation | Calculation of the PageRank for NITP took 0.022880077362060547s
Interlinking | Calculation of Degree of Connection for NITP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for NITP took 7.295608520507812e-05s
Believability | Calculation of trust value for NITP took 8.821487426757812e-06s
INFO | --- Analysis for notIdentifier took 362.07255005836487s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.553794860839844e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.3677978515625s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02389669418334961s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0012018680572509766s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 4.863739013671875e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 8.58306884765625e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.2783238887786865s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 8.249282836914062e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.30790185928344727s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.02925896644592285s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0013027191162109375s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 4.3392181396484375e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 1.2636184692382812e-05s
INFO | --- Analysis for npg took 1.664729356765747s
Availability | SPARQL endpoint availability check for NPM took 6.651878356933594e-05s
Availability | VoID file availability check for NPM took 0.0003745555877685547s
Completeness | Calculation of interlinking completeness for NPM took 60.29298734664917s
Reputation | Calculation of the PageRank for NPM took 0.02268218994140625s
Interlinking | Calculation of Degree of Connection for NPM took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for NPM took 3.4332275390625e-05s
Believability | Calculation of trust value for NPM took 1.1444091796875e-05s
INFO | --- Analysis for npm took 182.55971574783325s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.024822473526000977s
Availability | VoID file availability check for NTNU special collections took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for NTNU special collections took 120.35883927345276s
Reputation | Calculation of the PageRank for NTNU special collections took 0.022589445114135742s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0011224746704101562s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 8.225440979003906e-05s
Believability | Calculation of trust value for NTNU special collections took 1.0967254638671875e-05s
INFO | --- Analysis for ntnusc took 482.64906764030457s
Availability | SPARQL endpoint availability check for links took 4.792213439941406e-05s
Availability | VoID file availability check for links took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for links took 0.3178722858428955s
Reputation | Calculation of the PageRank for links took 0.026076316833496094s
Interlinking | Calculation of Degree of Connection for links took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for links took 0.001317739486694336s
Interlinking | Calculation of Clustering coefficient for links took 6.914138793945312e-05s
Believability | Calculation of trust value for links took 8.821487426757812e-06s
INFO | --- Analysis for nugmyanmar took 61.64407968521118s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 6.914138793945312e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2933175563812256s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.021503448486328125s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00010967254638671875s
Believability | Calculation of trust value for NUTS (GeoVocab) took 1.1920928955078125e-05s
INFO | --- Analysis for nuts-geovocab took 60.970057010650635s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.5131523609161377s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.33981990814208984s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.021489858627319336s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0008509159088134766s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 9.202957153320312e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.1920928955078125e-05s
INFO | --- Analysis for nvd took 181.81624937057495s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.7265794277191162s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.34203553199768066s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 0.00010061264038085938s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.1682510375976562e-05s
INFO | --- Analysis for nvs took 246.48813009262085s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 8.535385131835938e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 60.34388589859009s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.02123284339904785s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001926422119140625s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for nytimes-linked-open-data took 61.82790684700012s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 0.00021791458129882812s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.36437249183654785s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.022187232971191406s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 2.9087066650390625e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 1.1920928955078125e-05s
INFO | --- Analysis for o-anc took 61.7489914894104s
Availability | SPARQL endpoint availability check for OANetzwerk took 8.559226989746094e-05s
Availability | VoID file availability check for OANetzwerk took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for OANetzwerk took 59.55224561691284s
Reputation | Calculation of the PageRank for OANetzwerk took 0.02132868766784668s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.600120544433594e-05s
Believability | Calculation of trust value for OANetzwerk took 1.3113021850585938e-05s
INFO | --- Analysis for oanetzwerk took 60.953022480010986s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 9.989738464355469e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.000804901123046875s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 60.07144808769226s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.02655959129333496s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0008785724639892578s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 5.412101745605469e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 9.298324584960938e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 480.8337848186493s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.7478842735290527s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006301403045654297s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.909226417541504s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 2.2495296001434326s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 0.3557767868041992s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.8827579021453857s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.40529656410217s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 0.47320008277893066s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.3571789264678955s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.437713623046875s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.7254769802093506s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.5856633186340332s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.4576680660247803s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.50989603996277s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.41019487380981445s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.29375171661376953s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.9436182975769043s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.48899126052856445s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.9587869644165039s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 1.0109310150146484s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 13.199696063995361s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 9.72747802734375e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.5560343265533447s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.2822868824005127s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.2452375888824463s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.26550722122192383s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.5438821315765381s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.9880650043487549s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.44003868103027344s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.991554021835327s
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.43332338333129883s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 1.1375041007995605s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.03160738945007324s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.03099513053894043s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.31328487396240234s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.411509990692139s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.5842738151550293s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.2848548889160156s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.3609254360198975s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.448884010314941s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03206038475036621s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.42434048652648926s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.37879157066345215s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 23.5108904838562s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 119.8715169429779s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02106189727783203s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010585784912109375s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.2874603271484375e-05s
INFO | --- Analysis for ocd took 576.4661784172058s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 8.606910705566406e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0008325576782226562s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.3088414669036865s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.023341655731201172s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.52587890625e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.001062631607055664s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 5.245208740234375e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 0.00020551681518554688s
INFO | --- Analysis for oceandrilling-borehole took 2.958491563796997s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 2.3643131256103516s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.3834702968597412s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.021026134490966797s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.106231689453125e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.2874603271484375e-05s
INFO | --- Analysis for oceandrilling-codices took 6.694296598434448s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.8839988708496094s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.30197763442993164s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020841360092163086s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.838539123535156e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 4.560150146484375s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.9531199932098389s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.28496742248535156s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.0209043025970459s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 4.291534423828125e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.0967254638671875e-05s
INFO | --- Analysis for oceandrilling-forams took 64.04228925704956s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.8967909812927246s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0008041858673095703s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.3518552780151367s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020973682403564453s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.933906555175781e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-janus took 123.48597288131714s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 11.344275712966919s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0008528232574462891s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.3130669593811035s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.337860107421875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-janusamp took 14.2879056930542s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.3041627407073975s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2953152656555176s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.02175116539001465s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0009829998016357422s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.528594970703125e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1920928955078125e-05s
INFO | --- Analysis for oceandrilling-ldeo took 4.772872686386108s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 8.58306884765625e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 120.31264519691467s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02513718605041504s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 3.24249267578125e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.001316070556640625s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 8.749961853027344e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.2636184692382812e-05s
INFO | --- Analysis for oclc-fast took 363.52411556243896s
Availability | SPARQL endpoint availability check for Open Data Communities took 0.0001010894775390625s
Availability | VoID file availability check for Open Data Communities took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.30797672271728516s
Reputation | Calculation of the PageRank for Open Data Communities took 0.0213320255279541s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.314018249511719e-05s
Believability | Calculation of trust value for Open Data Communities took 1.33514404296875e-05s
INFO | --- Analysis for odc took 120.84721827507019s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.036064147949219e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.2879946231842041s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.023311138153076172s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0010399818420410156s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.6716461181640625e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.1682510375976562e-05s
INFO | --- Analysis for odc-imd-environment-score took 64.0041491985321s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 8.606910705566406e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.30943775177001953s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.02337646484375s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0010571479797363281s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 3.7670135498046875e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 1.2636184692382812e-05s
INFO | --- Analysis for odc-imd-rank-2007 took 1.7604529857635498s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.16262364387512207s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005843639373779297s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.2414543628692627s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 1.0924289226531982s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.19914960861206055s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.7101428508758545s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.39615702629089355s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 0.20753216743469238s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.09927010536193848s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.13827919960021973s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.13124966621398926s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 48.79650115966797s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.1481633186340332s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.24840545654297s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.24525856971740723s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.14487266540527344s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.4607357978820801s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.1699848175048828s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.25637245178222656s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.2544834613800049s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 10.957548379898071s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 9.5367431640625e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.31468939781188965s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.22462868690490723s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.14166617393493652s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.21745896339416504s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.1943202018737793s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.20162510871887207s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.2612764835357666s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.2277514934539795s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.20732975006103516s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.13803935050964355s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.21594858169555664s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.2109675407409668s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.6396772861480713s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.881072759628296s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.7388789653778076s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.00014138221740722656s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.6569254398345947s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.1790928840637207s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.5107042789459229s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02140355110168457s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 0.00013446807861328125s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 1.5497207641601562e-05s
INFO | --- Analysis for odc-lsoa took 650.4385137557983s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 8.749961853027344e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.285031795501709s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.021097421646118164s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 1.4066696166992188e-05s
INFO | --- Analysis for odc-population-2005 took 1.71333646774292s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 8.511543273925781e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 180.28530430793762s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.026060819625854492s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.001474618911743164s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 0.00010418891906738281s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 1.239776611328125e-05s
INFO | --- Analysis for ods took 421.56884717941284s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.10182452201843262s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2955904006958008s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02217721939086914s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00010919570922851562s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for oecd-linked-data took 61.794742822647095s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.839897155761719e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 59.80176520347595s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.02706146240234375s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 4.172325134277344e-05s
Believability | Calculation of trust value for Offener Haushalt took 1.2159347534179688e-05s
INFO | --- Analysis for offener-haushalt took 419.94087624549866s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.234898805618286s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.3100886344909668s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.8160552978515625e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.1444091796875e-05s
INFO | --- Analysis for ogolod took 190.66735553741455s
Availability | SPARQL endpoint availability check for OLAC Metadata took 8.940696716308594e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0008060932159423828s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.3323349952697754s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.02113485336303711s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.363059997558594e-05s
Believability | Calculation of trust value for OLAC Metadata took 5.9604644775390625e-06s
INFO | --- Analysis for olac took 81.6750738620758s
Availability | SPARQL endpoint availability check for OLiA took 8.916854858398438e-05s
Availability | VoID file availability check for OLiA took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for OLiA took 180.22997045516968s
Reputation | Calculation of the PageRank for OLiA took 0.021046161651611328s
Interlinking | Calculation of Degree of Connection for OLiA took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.0001304149627685547s
Believability | Calculation of trust value for OLiA took 1.2874603271484375e-05s
INFO | --- Analysis for olia took 370.94464325904846s
Availability | SPARQL endpoint availability check for OLiA Discourse took 5.14984130859375e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.3086674213409424s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02515578269958496s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0014235973358154297s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 5.459785461425781e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.1444091796875e-05s
INFO | --- Analysis for olia-discourse took 6.967080354690552s
Availability | SPARQL endpoint availability check for Open Land Use took 0.326416015625s
Availability | VoID file availability check for Open Land Use took 0.0005748271942138672s
Extra | Recovery of all triples for Open Land Use took 108.1512885093689s
Performance | Total latancy measurement for Open Land Use took 1.0141282081604004s
Amount of data | Number of triples check for Open Land Use took 9.483850717544556s
Interoperability | New terms check for Open Land Use took 14.154818058013916s
Versatility | Languages check for Open Land Use took 300.24676060676575s
Interpretability | Number of blank nodes check for Open Land Use took 2.2391574382781982s
Interpretability | RDF structures check for Open Land Use took 0.3260195255279541s
Versatility | Serialization formats check for Open Land Use took 0.7303991317749023s
Availability | RDF dump link check for Open Land Use took 0.31291937828063965s
License | MR license check for Open Land Use took 0.8009796142578125s
License | HR license check for Open Land Use took 300.2315857410431s
Amount of data | Number of property check for Open Land Use took 0.20299720764160156s
Understandability | Number of label check for Open Land Use took 2.3974759578704834s
Understandability | URI regex check for Open Land Use took 1.1106038093566895s
Understandability | Vocabs check for Open Land Use took 0.4599578380584717s
Verifiability | Authors check for Open Land Use took 0.20470762252807617s
Verifiability | Publishers check for Open Land Use took 2.9222376346588135s
Performance | Throughput check for Open Land Use took 11.194905519485474s
Amount of data | Check the number of entities for Open Land Use took 9.655952453613281e-05s
Verifiability | Contribs. check for Open Land Use took 0.18004369735717773s
Interlinking | sameAs chians check for Open Land Use took 0.20676422119140625s
Interlinking | skos check for Open Land Use took 0.45976853370666504s
Interlinking | skos check for Open Land Use took 0.39519643783569336s
Timeliness | dataset update frequency check for Open Land Use took 0.7699136734008789s
Currency | Creation date check for Open Land Use took 1.1526641845703125s
Currency | Modification date check for Open Land Use took 0.2559812068939209s
Rep.Conc. | URIs length for Open Land Use took 147.77456760406494s
Interoperability | New vocabularies check for Open Land Use took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.2053689956665039s
Accuracy | Check Functional Property for Open Land Use took 0.3973977565765381s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.4176199436187744s
Accuracy | Check Empty annotation labels for Open Land Use took 33.23331570625305s
Accuracy | Check White space in annotation for Open Land Use took 2.762747049331665s
Accuracy | Check Datatype consistency for Open Land Use took 2.8533074855804443s
Consistency | Disjoint class check for Open Land Use took 0.18029212951660156s
Consistency | Check Misplaced properties for Open Land Use took 87.09700036048889s
Consistency | Misplaced classes for Open Land Use took 8.720654249191284s
Consistency | Check Ontology hijacking for Open Land Use took 33.08927059173584s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.4792559146881104s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 86.4518473148346s
Conciseness | Check Extensional conciseness for Open Land Use took 2.9510672092437744s
Conciseness | Check Intensional conciseness for Open Land Use took 0.47443056106567383s
Security | Sign check for Open Land Use took 1.235307216644287s
Availability | Check URIs Dereferenciability for Open Land Use took 17.00823950767517s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.5325067043304443s
Reputation | Calculation of the PageRank for Open Land Use took 0.021717071533203125s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Land Use took 1.2159347534179688e-05s
INFO | --- Analysis for OLU took 2246.343411922455s
Availability | SPARQL endpoint availability check for OmegaWiki took 8.606910705566406e-05s
Availability | VoID file availability check for OmegaWiki took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.3387587070465088s
Reputation | Calculation of the PageRank for OmegaWiki took 0.023424625396728516s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0011508464813232422s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 4.553794860839844e-05s
Believability | Calculation of trust value for OmegaWiki took 1.2636184692382812e-05s
INFO | --- Analysis for omegawiki took 121.47389149665833s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.7172057628631592s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.00031638145446777344s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.3805065155029297s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.035355329513549805s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0017321109771728516s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 6.508827209472656e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-als took 2.6570565700531006s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.3155341148376465s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00039196014404296875s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2936270236968994s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.022693634033203125s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0010476112365722656s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 6.270408630371094e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-arb took 121.29393243789673s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.31464552879333496s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2939128875732422s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.02240896224975586s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0010378360748291016s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 4.506111145019531e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-bul took 61.85827302932739s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2843308448791504s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.27190232276916504s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020970821380615234s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 4.601478576660156e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-cow took 61.87001419067383s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.29291534423828125s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 120.36408472061157s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02157282829284668s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0014331340789794922s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-cwn took 361.5318400859833s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.35277271270751953s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.3071002960205078s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.022212505340576172s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007932186126708984s
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.2159347534179688e-05s
INFO | --- Analysis for omwn-dan took 2.1357638835906982s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.3005380630493164s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.34922146797180176s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.021387577056884766s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007712841033935547s
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.1682510375976562e-05s
INFO | --- Analysis for omwn-ell took 2.03572416305542s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.30184221267700195s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.3036825656890869s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02163219451904297s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0009617805480957031s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 6.127357482910156e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-eng took 180.55722332000732s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.29593324661254883s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.36554479598999023s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02236342430114746s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.001348257064819336s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 5.91278076171875e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-fas took 2.2034640312194824s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2766444683074951s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 60.30759811401367s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.021466970443725586s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-fin took 62.01195025444031s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.3280620574951172s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 60.417351484298706s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.021166563034057617s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-fra took 361.42354559898376s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.34380030632019043s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.3555586338043213s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.021663188934326172s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-heb took 61.704145193099976s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2937436103820801s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.287355899810791s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 4.57763671875e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-hrv took 2.221215009689331s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2659013271331787s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.36905694007873535s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.02236199378967285s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00084686279296875s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 5.507469177246094e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-isl took 181.2610366344452s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.3041865825653076s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.35271477699279785s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-ita took 2.22172474861145s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.3431532382965088s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0003273487091064453s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.36583590507507324s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02585291862487793s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 5.7697296142578125e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-iwn took 361.36927604675293s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.30109596252441406s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2944979667663574s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.021675825119018555s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-jpn took 61.74833154678345s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.32368016242980957s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.3825979232788086s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.021210432052612305s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
INFO | --- Analysis for omwn-mcr took 61.884770154953s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2737891674041748s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2843043804168701s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 2.3603439331054688e-05s
INFO | --- Analysis for omwn-msa took 2.044185161590576s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.30345892906188965s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.29741382598876953s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02193307876586914s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-nld took 2.0808756351470947s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.3073713779449463s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.302107572555542s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.021366119384765625s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.601478576660156e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-nor took 61.5035765171051s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2477278709411621s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2934000492095947s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-pol took 2.0611088275909424s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.24154186248779297s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 59.53494477272034s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02120041847229004s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.553794860839844e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-por took 121.27966451644897s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.3828420639038086s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2945842742919922s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.021422386169433594s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 4.458427429199219e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-ron took 301.11061096191406s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.30126285552978516s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 59.9840612411499s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.021444320678710938s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.001058816909790039s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-slk took 61.81069803237915s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.28797435760498047s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.3873627185821533s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.02110743522644043s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 5.030632019042969e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-slv took 121.6002197265625s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.30504536628723145s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 60.030333280563354s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.022028207778930664s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 4.792213439941406e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-swe took 420.45429730415344s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.30399394035339355s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2930731773376465s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.035625457763671875s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0015802383422851562s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 8.702278137207031e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
INFO | --- Analysis for omwn-tha took 121.6680235862732s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 3.261920690536499s
Availability | VoID file availability check for OntoBeef Domain took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.3546111583709717s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 7.43865966796875e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.2874603271484375e-05s
INFO | --- Analysis for ontobeef-domain took 20.728076219558716s
Availability | SPARQL endpoint availability check for Ontos News Portal took 8.940696716308594e-05s
Availability | VoID file availability check for Ontos News Portal took 0.00039124488830566406s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.29200172424316406s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.34600830078125e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.2159347534179688e-05s
INFO | --- Analysis for ontos-news-portal took 3.542449712753296s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 8.58306884765625e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.35274171829223633s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.021238088607788086s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.1205673217773438e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 361.2014150619507s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 0.00010657310485839844s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.29658007621765137s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.021279335021972656s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.100799560546875e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.2636184692382812e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 145.04079008102417s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 8.440017700195312e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.3929429054260254s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.02107548713684082s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.956390380859375e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 1.2636184692382812e-05s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.0771524906158447s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 9.918212890625e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 59.62221813201904s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.91278076171875e-05s
Believability | Calculation of trust value for Open Data Euskadi took 1.2159347534179688e-05s
INFO | --- Analysis for open-data-euskadi took 486.64726662635803s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 9.894371032714844e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0003807544708251953s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.29789137840270996s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.021315574645996094s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0009164810180664062s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00011897087097167969s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.0728836059570312e-05s
INFO | --- Analysis for open-data-risp took 125.9210422039032s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.20288348197937012s
Availability | VoID file availability check for Open Data Thesaurus took 0.0007488727569580078s
Extra | Recovery of all triples for Open Data Thesaurus took 1.1882760524749756s
Performance | Total latancy measurement for Open Data Thesaurus took 0.50301194190979s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1212625503540039s
Interoperability | New terms check for Open Data Thesaurus took 1.5179944038391113s
Versatility | Languages check for Open Data Thesaurus took 0.13567900657653809s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.13060855865478516s
Security | Check HTTPS for Open Data Thesaurus took 0.3751716613769531s
Interpretability | RDF structures check for Open Data Thesaurus took 0.12751364707946777s
Versatility | Serialization formats check for Open Data Thesaurus took 0.13172316551208496s
Availability | RDF dump link check for Open Data Thesaurus took 1.1579484939575195s
License | MR license check for Open Data Thesaurus took 0.11637234687805176s
License | HR license check for Open Data Thesaurus took 0.09533953666687012s
Amount of data | Number of property check for Open Data Thesaurus took 0.1285719871520996s
Understandability | Number of label check for Open Data Thesaurus took 0.14623546600341797s
Understandability | URI regex check for Open Data Thesaurus took 0.17734766006469727s
Understandability | Vocabs check for Open Data Thesaurus took 0.11641502380371094s
Verifiability | Authors check for Open Data Thesaurus took 0.12538766860961914s
Verifiability | Publishers check for Open Data Thesaurus took 0.12248849868774414s
Performance | Throughput check for Open Data Thesaurus took 10.256945371627808s
Amount of data | Check the number of entities for Open Data Thesaurus took 9.918212890625e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.12334394454956055s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.12065720558166504s
Interlinking | skos check for Open Data Thesaurus took 0.13474273681640625s
Interlinking | skos check for Open Data Thesaurus took 0.0921485424041748s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.08144831657409668s
Currency | Creation date check for Open Data Thesaurus took 0.12040138244628906s
Currency | Modification date check for Open Data Thesaurus took 0.11977672576904297s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4814753532409668s
Interoperability | New vocabularies check for Open Data Thesaurus took 4.118793964385986s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11624455451965332s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.09229612350463867s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.09271430969238281s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.20436477661132812s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.001142740249633789s
Consistency | Disjoint class check for Open Data Thesaurus took 0.08376789093017578s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.20636940002441406s
Consistency | Misplaced classes for Open Data Thesaurus took 0.10016655921936035s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.5393242835998535s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.4535653591156006s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001373291015625s
Security | Sign check for Open Data Thesaurus took 0.08568453788757324s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.4010951519012451s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020188093185424805s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.867813110351562e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 5.136606693267822s
Believability | Calculation of trust value for Open Data Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for open-data-thesaurus took 141.10211181640625s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 8.463859558105469e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.3732781410217285s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020921945571899414s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 3.552436828613281e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 1.2874603271484375e-05s
INFO | --- Analysis for open-data-tor-vergata took 1.950901985168457s
Availability | SPARQL endpoint availability check for Open Election Data Project took 6.628036499023438e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 60.475786447525024s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.021853923797607422s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 8.034706115722656e-05s
Believability | Calculation of trust value for Open Election Data Project took 1.2159347534179688e-05s
INFO | --- Analysis for open-election-data-project took 361.9070248603821s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 2.478339910507202s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0007245540618896484s
Extra | Recovery of all triples for OpenEI - Open Energy Info took 5.263330459594727s
Performance | Total latancy measurement for OpenEI - Open Energy Info took 7.446241855621338s
Amount of data | Number of triples check for OpenEI - Open Energy Info took 3.2509047985076904s
Interoperability | New terms check for OpenEI - Open Energy Info took 4.540370941162109s
Versatility | Languages check for OpenEI - Open Energy Info took 1.4938929080963135s
Interpretability | Number of blank nodes check for OpenEI - Open Energy Info took 2.2423758506774902s
Security | Check HTTPS for OpenEI - Open Energy Info took 1.1224212646484375s
Interpretability | RDF structures check for OpenEI - Open Energy Info took 1.5099091529846191s
Versatility | Serialization formats check for OpenEI - Open Energy Info took 1.505427360534668s
Availability | RDF dump link check for OpenEI - Open Energy Info took 1.522157907485962s
License | MR license check for OpenEI - Open Energy Info took 1.5176856517791748s
License | HR license check for OpenEI - Open Energy Info took 8.58755373954773s
Amount of data | Number of property check for OpenEI - Open Energy Info took 1.5063145160675049s
Understandability | Number of label check for OpenEI - Open Energy Info took 2.1368255615234375s
Understandability | URI regex check for OpenEI - Open Energy Info took 2.9872946739196777s
Understandability | Vocabs check for OpenEI - Open Energy Info took 1.5262510776519775s
Verifiability | Authors check for OpenEI - Open Energy Info took 1.5151557922363281s
Verifiability | Publishers check for OpenEI - Open Energy Info took 1.517103672027588s
Performance | Throughput check for OpenEI - Open Energy Info took 15.12080192565918s
Amount of data | Check the number of entities for OpenEI - Open Energy Info took 0.0001201629638671875s
Verifiability | Contribs. check for OpenEI - Open Energy Info took 1.5009891986846924s
Interlinking | sameAs chians check for OpenEI - Open Energy Info took 1.5204195976257324s
Interlinking | skos check for OpenEI - Open Energy Info took 1.4700939655303955s
Interlinking | skos check for OpenEI - Open Energy Info took 1.4642367362976074s
Timeliness | dataset update frequency check for OpenEI - Open Energy Info took 1.463038444519043s
Currency | Creation date check for OpenEI - Open Energy Info took 1.5269279479980469s
Currency | Modification date check for OpenEI - Open Energy Info took 1.5220882892608643s
Rep.Conc. | URIs length for OpenEI - Open Energy Info took 16.697561264038086s
Interoperability | New vocabularies check for OpenEI - Open Energy Info took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for OpenEI - Open Energy Info took 1.4818840026855469s
Accuracy | Check Functional Property for OpenEI - Open Energy Info took 1.4843785762786865s
Accuracy | Check Inverse Functional Property for OpenEI - Open Energy Info took 1.5056743621826172s
Accuracy | Check Empty annotation labels for OpenEI - Open Energy Info took 2.857940912246704s
Accuracy | Check White space in annotation for OpenEI - Open Energy Info took 0.03235745429992676s
Accuracy | Check Datatype consistency for OpenEI - Open Energy Info took 0.0289459228515625s
Consistency | Disjoint class check for OpenEI - Open Energy Info took 1.5426888465881348s
Consistency | Check Misplaced properties for OpenEI - Open Energy Info took 15.443346977233887s
Consistency | Misplaced classes for OpenEI - Open Energy Info took 2.4496779441833496s
Consistency | Check Ontology hijacking for OpenEI - Open Energy Info took 4.212228536605835s
Consistency | Check Invalid usage of undefined classes for OpenEI - Open Energy Info took 1.3787837028503418s
Consistency | Check Invalid usage of undefined properties for OpenEI - Open Energy Info took 3.7442715167999268s
Conciseness | Check Extensional conciseness for OpenEI - Open Energy Info took 0.03416085243225098s
Conciseness | Check Intensional conciseness for OpenEI - Open Energy Info took 2.399951219558716s
Security | Sign check for OpenEI - Open Energy Info took 1.5352051258087158s
Availability | Check URIs Dereferenciability for OpenEI - Open Energy Info took 23.977874755859375s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 120.29044485092163s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02618575096130371s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.001001119613647461s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.00012540817260742188s
Interoperability | Check the re-using of existing vocabs for OpenEI - Open Energy Info took 2.1457672119140625e-06s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 1.6927719116210938e-05s
INFO | --- Analysis for open-energy-info-wiki took 937.0255725383759s
Availability | SPARQL endpoint availability check for Open Library took 0.0001010894775390625s
Availability | VoID file availability check for Open Library took 0.0008428096771240234s
Completeness | Calculation of interlinking completeness for Open Library took 0.37709736824035645s
Reputation | Calculation of the PageRank for Open Library took 0.021376371383666992s
Interlinking | Calculation of Degree of Connection for Open Library took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.486343383789062e-05s
Believability | Calculation of trust value for Open Library took 6.4373016357421875e-06s
INFO | --- Analysis for open-library took 250.01372647285461s
Availability | SPARQL endpoint availability check for Open Directory took 8.630752563476562e-05s
Availability | VoID file availability check for Open Directory took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Open Directory took 0.295529842376709s
Reputation | Calculation of the PageRank for Open Directory took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.314018249511719e-05s
Believability | Calculation of trust value for Open Directory took 1.2159347534179688e-05s
INFO | --- Analysis for open_directory took 121.77341341972351s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.6017119884490967s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0008113384246826172s
Extra | Recovery of all triples for Open Land Use @PSNC took 107.56401801109314s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9860997200012207s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.057566404342651s
Interoperability | New terms check for Open Land Use @PSNC took 14.143804550170898s
Versatility | Languages check for Open Land Use @PSNC took 300.21196937561035s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.1174371242523193s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.279909610748291s
Versatility | Serialization formats check for Open Land Use @PSNC took 0.6875460147857666s
Availability | RDF dump link check for Open Land Use @PSNC took 0.33303236961364746s
License | MR license check for Open Land Use @PSNC took 0.8021688461303711s
License | HR license check for Open Land Use @PSNC took 300.2306971549988s
Amount of data | Number of property check for Open Land Use @PSNC took 0.21972322463989258s
Understandability | Number of label check for Open Land Use @PSNC took 2.801661729812622s
Understandability | URI regex check for Open Land Use @PSNC took 1.308063268661499s
Understandability | Vocabs check for Open Land Use @PSNC took 0.5180847644805908s
Verifiability | Authors check for Open Land Use @PSNC took 0.20102190971374512s
Verifiability | Publishers check for Open Land Use @PSNC took 2.9360079765319824s
Performance | Throughput check for Open Land Use @PSNC took 11.494426727294922s
Amount of data | Check the number of entities for Open Land Use @PSNC took 9.72747802734375e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.19453096389770508s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.19134187698364258s
Interlinking | skos check for Open Land Use @PSNC took 0.5083427429199219s
Interlinking | skos check for Open Land Use @PSNC took 0.3970065116882324s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 0.45441246032714844s
Currency | Creation date check for Open Land Use @PSNC took 1.186955213546753s
Currency | Modification date check for Open Land Use @PSNC took 0.23743724822998047s
Rep.Conc. | URIs length for Open Land Use @PSNC took 148.34098863601685s
Interoperability | New vocabularies check for Open Land Use @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.20830821990966797s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.46108484268188477s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.45444464683532715s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 36.641844511032104s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.7368435859680176s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.6717000007629395s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.1790151596069336s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 86.93370914459229s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.585227251052856s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 31.29414415359497s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.420396327972412s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 87.09702157974243s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.9604930877685547s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.5343749523162842s
Security | Sign check for Open Land Use @PSNC took 1.0391523838043213s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 17.17828369140625s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 120.30991101264954s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02252817153930664s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.3113021850585938e-05s
INFO | --- Analysis for Open_Land_Use took 2426.5438318252563s
Availability | SPARQL endpoint availability check for flyatlas took 1.252333641052246s
Availability | VoID file availability check for flyatlas took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for flyatlas took 0.31108570098876953s
Reputation | Calculation of the PageRank for flyatlas took 0.022581815719604492s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.52587890625e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0010845661163330078s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.886222839355469e-05s
Believability | Calculation of trust value for flyatlas took 1.1920928955078125e-05s
INFO | --- Analysis for openbiomed-flyatlas took 4.045082092285156s
Availability | SPARQL endpoint availability check for OpenCalais took 8.606910705566406e-05s
Availability | VoID file availability check for OpenCalais took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.3699977397918701s
Reputation | Calculation of the PageRank for OpenCalais took 0.020769834518432617s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00013136863708496094s
Believability | Calculation of trust value for OpenCalais took 1.3113021850585938e-05s
INFO | --- Analysis for opencalais took 5.2165749073028564s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 8.797645568847656e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.36957573890686035s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.021416187286376953s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 8.106231689453125e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 1.1205673217773438e-05s
INFO | --- Analysis for opencorporates took 121.65344166755676s
Availability | SPARQL endpoint availability check for OpenCyc took 6.961822509765625e-05s
Availability | VoID file availability check for OpenCyc took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2832319736480713s
Reputation | Calculation of the PageRank for OpenCyc took 0.02331399917602539s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0010886192321777344s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.0001537799835205078s
Believability | Calculation of trust value for OpenCyc took 1.3113021850585938e-05s
INFO | --- Analysis for opencyc took 300.6822564601898s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 9.870529174804688e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.40908336639404297s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.021654605865478516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.886222839355469e-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 181.83508801460266s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 9.083747863769531e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.32892942428588867s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02506852149963379s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0013670921325683594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 6.222724914550781e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.510272979736328s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.00012063980102539062s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 60.02263116836548s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.022509098052978516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0010173320770263672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 6.961822509765625e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 62.48563504219055s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 8.726119995117188e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 59.983083963394165s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.021799564361572266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 5.245208740234375e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 361.20463347435s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2909395694732666s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.022509098052978516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 121.74867796897888s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 9.083747863769531e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.3215789794921875s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.021167755126953125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 5.012587785720825s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 0.00010037422180175781s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.30775976181030273s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.03381085395812988s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0016832351684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 0.00011205673217773438s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 62.597352743148804s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.988380432128906e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.30816030502319336s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.02848219871520996s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0013434886932373047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00010824203491210938s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.771186113357544s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0001251697540283203s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.3899257183074951s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.023409366607666016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.696846008300781e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 363.3251516819s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 0.00010347366333007812s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 59.888322591781616s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.021187543869018555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.887580871582031e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 181.23787212371826s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.3420553207397461s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.02144789695739746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0010662078857421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 6.985664367675781e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 182.2425572872162s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 5.984306335449219e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 180.3164839744568s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.022730588912963867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0009243488311767578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 5.269050598144531e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 302.5550196170807s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 9.608268737792969e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.28813958168029785s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.021591901779174805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0008184909820556641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 5.054473876953125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 121.14367318153381s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 5.054473876953125e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 60.31076979637146s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02416682243347168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0010366439819335938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.839897155761719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 120.8042311668396s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 9.369850158691406e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 59.83638334274292s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02120184898376465s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 6.0558319091796875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 362.1035089492798s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.00010538101196289062s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.3691396713256836s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.021037817001342773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.566298246383667s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.083747863769531e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.3084444999694824s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02156805992126465s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 62.245402097702026s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 0.00011205673217773438s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 59.85647630691528s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02159714698791504s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 62.88500761985779s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 9.083747863769531e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.3569808006286621s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.022109270095825195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007715225219726562s
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.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 1.759892463684082s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.846687316894531e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2850520610809326s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 62.72550940513611s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 8.749961853027344e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.27335047721862793s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.022845745086669922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.001043558120727539s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 362.5903265476227s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 0.00010633468627929688s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2883036136627197s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02523946762084961s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0011317729949951172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 5.054473876953125e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 63.353633880615234s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.696846008300781e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.3024303913116455s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.02136540412902832s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 5.14984130859375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 123.89658093452454s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.00010800361633300781s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 120.1075427532196s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.024580955505371094s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0010437965393066406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 8.153915405273438e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 422.249858379364s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.744529724121094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.3148343563079834s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.021332502365112305s
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.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 63.02624821662903s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 9.179115295410156e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0008301734924316406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.3845398426055908s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.028776884078979492s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0014200210571289062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 6.818771362304688e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 63.5700147151947s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.00010347366333007812s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2909679412841797s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0222475528717041s
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.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 62.099693775177s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.673004150390625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.30156445503234863s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02129077911376953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0008399486541748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.663093090057373s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 8.916854858398438e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.3782684803009033s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.021441936492919922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.499914884567261s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.32869935035705566s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.023641347885131836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0011734962463378906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.963180541992188e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.1785190105438232s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 8.869171142578125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2965404987335205s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.021383047103881836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 62.45941424369812s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.226799011230469e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.3486971855163574s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.021405458450317383s
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.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.5362730026245117s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.036064147949219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 120.27189803123474s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.03638505935668945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 5.364418029785156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 362.566522359848s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00010800361633300781s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 59.76982140541077s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.026485443115234375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0015616416931152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.416175842285156e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 121.0172688961029s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00011539459228515625s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.29787302017211914s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.02162933349609375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 61.48240423202515s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 8.678436279296875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007240772247314453s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.3123054504394531s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0223391056060791s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0008273124694824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.233443021774292s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.059906005859375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007889270782470703s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 59.726526975631714s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02155613899230957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.5974044799804688e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 301.65987849235535s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 9.608268737792969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.3585929870605469s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.021925687789916992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 6.4849853515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 181.851948261261s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.28756117820739746s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.025391578674316406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0014264583587646484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 9.250640869140625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 61.96637749671936s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.7738037109375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.00075531005859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2973051071166992s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.025170326232910156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.001447439193725586s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 7.176399230957031e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.8596649169921875e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 62.71430253982544s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 5.936622619628906e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0008325576782226562s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.3362865447998047s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.022127389907836914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 5.555152893066406e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.5020370483398438e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 600.6608047485352s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 9.012222290039062e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.34787917137145996s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.022026538848876953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.461103677749634s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 5.269050598144531e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2926454544067383s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02204155921936035s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 122.83332657814026s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.0329625606536865s
Availability | VoID file availability check for Open Data of Ecuador took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 59.628103494644165s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.021178483963012695s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 9.655952453613281e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.1682510375976562e-05s
INFO | --- Analysis for opendataec took 364.6301119327545s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.00013065338134765625s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 60.45450162887573s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.022101640701293945s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.239776611328125e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 363.4657452106476s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 0.0001571178436279297s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0007958412170410156s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.3494584560394287s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.021681547164916992s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.3828277587890625e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 122.77783632278442s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 8.893013000488281e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.3179466724395752s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.021472692489624023s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.3906428813934326s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 0.00010967254638671875s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.3429999351501465s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.021175146102905273s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.33514404296875e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 122.50889039039612s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.410743713378906e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.3641948699951172s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.021340608596801758s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.1682510375976562e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 62.92849898338318s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 8.7738037109375e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.3702068328857422s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02154231071472168s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.0967254638671875e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.932408332824707s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 8.96453857421875e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 59.80750060081482s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02387714385986328s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 5.6743621826171875e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 181.8659484386444s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 0.00010633468627929688s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.3214111328125s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.0216066837310791s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 5.4836273193359375e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 5.91278076171875e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 302.5437912940979s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 5.125999450683594e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.41364431381225586s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.022745847702026367s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.696846008300781e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.6927719116210938e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 181.77980065345764s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 31.749595880508423s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2827165126800537s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.021052837371826172s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.24249267578125e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.6450881958007812e-05s
INFO | --- Analysis for openlink-lod-cache took 332.78632402420044s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 8.869171142578125e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.30072784423828125s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.022670745849609375s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 2.288818359375e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0010287761688232422s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 0.00013327598571777344s
Believability | Calculation of trust value for openlinksw dataspaces took 8.106231689453125e-06s
INFO | --- Analysis for openlinksw-dataspaces took 62.25284814834595s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 5.817413330078125e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.41193509101867676s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.02197432518005371s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0010597705841064453s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 0.00012350082397460938s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 7.62939453125e-06s
INFO | --- Analysis for openlylocal took 71.9467396736145s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.8235664367675781s
Availability | VoID file availability check for OpenMobileNetwork took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2890300750732422s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.022905826568603516s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.001226663589477539s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 0.00010061264038085938s
Believability | Calculation of trust value for OpenMobileNetwork took 8.821487426757812e-06s
INFO | --- Analysis for openmobilenetwork took 3.0712790489196777s
Availability | SPARQL endpoint availability check for OpenTox took 8.893013000488281e-05s
Availability | VoID file availability check for OpenTox took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for OpenTox took 0.3083810806274414s
Reputation | Calculation of the PageRank for OpenTox took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for OpenTox took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenTox took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenTox took 1.239776611328125e-05s
INFO | --- Analysis for opentox took 1.8390958309173584s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 8.654594421386719e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.3243215084075928s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.02150130271911621s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.075599670410156e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 2.3365020751953125e-05s
INFO | --- Analysis for openuplabs took 61.16568613052368s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 8.606910705566406e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.36832237243652344s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.021607160568237305s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0013861656188964844s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 4.9114227294921875e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 1.3589859008789062e-05s
INFO | --- Analysis for opus took 2.0995659828186035s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 8.535385131835938e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.29625844955444336s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.021185874938964844s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.6716461181640625e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 1.2636184692382812e-05s
INFO | --- Analysis for orcid took 61.60874390602112s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9772036075592041s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.3300352096557617s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.021791696548461914s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.00011324882507324219s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 363.8620970249176s
Availability | SPARQL endpoint availability check for oreilly took 8.96453857421875e-05s
Availability | VoID file availability check for oreilly took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for oreilly took 59.910550594329834s
Reputation | Calculation of the PageRank for oreilly took 0.021637916564941406s
Interlinking | Calculation of Degree of Connection for oreilly took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for oreilly took 6.604194641113281e-05s
Believability | Calculation of trust value for oreilly took 1.3113021850585938e-05s
INFO | --- Analysis for oreilly took 300.7159698009491s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 4.03702712059021s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.3337435722351074s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.026627540588378906s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.001451253890991211s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 7.343292236328125e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.33514404296875e-05s
INFO | --- Analysis for Organchem-Data took 364.2169015407562s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.07517433166503906s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.30501317977905273s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020982027053833008s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.794929504394531e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for organic-edunet took 8.975131034851074s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.506317138671875s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005807876586914062s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 6.3930275440216064s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.9088819026947021s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.19315028190612793s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.8335402011871338s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 4.76707911491394s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.19738125801086426s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.2909276485443115s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.18245410919189453s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.17987346649169922s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.20988106727600098s
License | HR license check for Open Research Knowledge Graph (ORKG) took 2.748960256576538s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.17462706565856934s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.20160508155822754s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.3629281520843506s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.21005773544311523s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.19440817832946777s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.17069292068481445s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 11.058448314666748s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 8.559226989746094e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.1954491138458252s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.1822967529296875s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1996932029724121s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.20326852798461914s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1815662384033203s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.19899344444274902s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.2106950283050537s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 3.8914995193481445s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 3.600120544433594e-05s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.17749738693237305s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.18243169784545898s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.18190646171569824s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.4270505905151367s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.21113944053649902s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2804396152496338s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.22902584075927734s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.3457708358764648s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.9239730834960938s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.3934855461120605s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.413362741470337s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.236833333969116s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.30437278747558594s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.19692182540893555s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.18407464027404785s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2079.354420900345s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.722553014755249s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021601200103759766s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 0.00013375282287597656s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.3113021850585938e-05s
INFO | --- Analysis for orkg took 2396.295599460602s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.078317165374756s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.38070225715637207s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.023034095764160156s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0009984970092773438s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 0.00011777877807617188s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.1920928955078125e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 144.9100227355957s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.5878937244415283s
Availability | VoID file availability check for OSM Semantic Network took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.33426380157470703s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.021747112274169922s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.743171691894531e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.2159347534179688e-05s
INFO | --- Analysis for osm-semantic-network took 6.65112566947937s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.7147650718688965s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00034809112548828125s
Extra | Recovery of all triples for Open Transport Map @PSNC took 109.2307505607605s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.9894671440124512s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.509413480758667s
Interoperability | New terms check for Open Transport Map @PSNC took 14.07474136352539s
Versatility | Languages check for Open Transport Map @PSNC took 300.23174810409546s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 2.2739059925079346s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.27718257904052734s
Versatility | Serialization formats check for Open Transport Map @PSNC took 0.5982637405395508s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.3586084842681885s
License | MR license check for Open Transport Map @PSNC took 0.8478891849517822s
License | HR license check for Open Transport Map @PSNC took 300.2445933818817s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.18877220153808594s
Understandability | Number of label check for Open Transport Map @PSNC took 2.223616123199463s
Understandability | URI regex check for Open Transport Map @PSNC took 1.2815992832183838s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.37697625160217285s
Verifiability | Authors check for Open Transport Map @PSNC took 0.19015145301818848s
Verifiability | Publishers check for Open Transport Map @PSNC took 3.000103235244751s
Performance | Throughput check for Open Transport Map @PSNC took 11.123645067214966s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 0.00012111663818359375s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.18058109283447266s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.2126612663269043s
Interlinking | skos check for Open Transport Map @PSNC took 0.4771127700805664s
Interlinking | skos check for Open Transport Map @PSNC took 0.4229111671447754s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 0.5877313613891602s
Currency | Creation date check for Open Transport Map @PSNC took 1.1756162643432617s
Currency | Modification date check for Open Transport Map @PSNC took 0.24770212173461914s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 149.75879836082458s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.180769681930542s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.41289544105529785s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.28974342346191406s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 40.41189646720886s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.7046360969543457s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.6389262676239014s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.25176000595092773s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 86.38890027999878s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.522887468338013s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 30.968933820724487s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.4152882099151611s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 87.23480725288391s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.9667093753814697s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.49689555168151855s
Security | Sign check for Open Transport Map @PSNC took 1.348233938217163s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 15.730600118637085s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 120.5738730430603s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.021504878997802734s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for OTM took 2605.854664325714s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 8.0108642578125e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0003173351287841797s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.3975710868835449s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.021268367767333984s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.24249267578125e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 1.2874603271484375e-05s
INFO | --- Analysis for ounl-dspace-in-rdf took 121.72464036941528s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 9.131431579589844e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 119.71664214134216s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.021498441696166992s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.814697265625e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.4543533325195312e-05s
INFO | --- Analysis for ox-ac-uk-catalogue took 180.6322844028473s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 8.869171142578125e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.29569005966186523s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 2.8371810913085938e-05s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 181.06039190292358s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 9.083747863769531e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.3773972988128662s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020911693572998047s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 2.6464462280273438e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 1.2636184692382812e-05s
INFO | --- Analysis for ox-ac-uk-openmeters took 61.88608169555664s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 9.1552734375e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.32314300537109375s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.021202564239501953s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 4.029273986816406e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 1.2636184692382812e-05s
INFO | --- Analysis for ox-ac-uk-timeseries took 61.73252844810486s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 0.00013256072998046875s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.4610862731933594s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.021361827850341797s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 1.33514404296875e-05s
INFO | --- Analysis for ox-ac-uk-vacancies took 121.96281480789185s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 8.559226989746094e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2947728633880615s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.123283386230469e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 1.9073486328125e-05s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 360.7475526332855s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 8.988380432128906e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.3067893981933594s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.021130084991455078s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.86102294921875e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 1.239776611328125e-05s
INFO | --- Analysis for oxpoints took 60.90053963661194s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.4558377265930176s
Availability | VoID file availability check for Pali English Lexicon took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 59.93414258956909s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.022251129150390625s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0008451938629150391s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 4.029273986816406e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.2636184692382812e-05s
INFO | --- Analysis for pali-english-lexicon took 364.0285840034485s
Availability | SPARQL endpoint availability check for PanLex took 2.3554883003234863s
Availability | VoID file availability check for PanLex took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for PanLex took 0.2923119068145752s
Reputation | Calculation of the PageRank for PanLex took 0.021204233169555664s
Interlinking | Calculation of Degree of Connection for PanLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PanLex took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.724761962890625e-05s
Believability | Calculation of trust value for PanLex took 1.1205673217773438e-05s
INFO | --- Analysis for panlex took 182.8336842060089s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.601478576660156e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.305225133895874s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.023104190826416016s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.7670135498046875e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.239776611328125e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 123.62934947013855s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.04428815841674805s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2962532043457031s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.021186351776123047s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.054473876953125e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.2874603271484375e-05s
INFO | --- Analysis for patents-data-gov-uk took 360.9245550632477s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 0.00010156631469726562s
Availability | VoID file availability check for PDEV-Lemon took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 59.777042627334595s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02283930778503418s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 5.364418029785156e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.33514404296875e-05s
INFO | --- Analysis for pdev-lemon took 122.29931640625s
Availability | SPARQL endpoint availability check for pdevlemon took 9.202957153320312e-05s
Availability | VoID file availability check for pdevlemon took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.28444790840148926s
Reputation | Calculation of the PageRank for pdevlemon took 0.02294015884399414s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.9802322387695312e-05s
Believability | Calculation of trust value for pdevlemon took 1.1444091796875e-05s
INFO | --- Analysis for pdevlemon took 62.01382493972778s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 9.72747802734375e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008611679077148438s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.3348667621612549s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.022440433502197266s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 9.298324584960938e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.1682510375976562e-05s
INFO | --- Analysis for periodo took 77.18518805503845s
Availability | SPARQL endpoint availability check for Personal_Homepages took 0.000102996826171875s
Availability | VoID file availability check for Personal_Homepages took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.36678314208984375s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0004119873046875s
Believability | Calculation of trust value for Personal_Homepages took 1.430511474609375e-05s
INFO | --- Analysis for personal-homepages took 61.444015979766846s
Availability | SPARQL endpoint availability check for Ontology of University People took 9.1552734375e-05s
Availability | VoID file availability check for Ontology of University People took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.3884093761444092s
Reputation | Calculation of the PageRank for Ontology of University People took 0.021840572357177734s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 4.887580871582031e-05s
Believability | Calculation of trust value for Ontology of University People took 1.2636184692382812e-05s
INFO | --- Analysis for PersonOnto took 1.819258689880371s
Availability | SPARQL endpoint availability check for PGxLOD took 0.42052149772644043s
Availability | VoID file availability check for PGxLOD took 0.0007543563842773438s
Extra | Recovery of all triples for PGxLOD took 0.9939353466033936s
Performance | Total latancy measurement for PGxLOD took 0.8726584911346436s
Amount of data | Number of triples check for PGxLOD took 3.6565678119659424s
Interoperability | New terms check for PGxLOD took 1.8868863582611084s
Versatility | Languages check for PGxLOD took 60.28470730781555s
Interpretability | Number of blank nodes check for PGxLOD took 1.5250954627990723s
Interpretability | RDF structures check for PGxLOD took 0.5762887001037598s
Versatility | Serialization formats check for PGxLOD took 0.21635055541992188s
Availability | RDF dump link check for PGxLOD took 15.634432077407837s
License | MR license check for PGxLOD took 0.4519062042236328s
License | HR license check for PGxLOD took 62.024494647979736s
Amount of data | Number of property check for PGxLOD took 0.2546539306640625s
Understandability | Number of label check for PGxLOD took 1.9142820835113525s
Understandability | URI regex check for PGxLOD took 0.40040063858032227s
Understandability | Vocabs check for PGxLOD took 0.22886085510253906s
Verifiability | Authors check for PGxLOD took 0.38492345809936523s
Verifiability | Publishers check for PGxLOD took 0.28488707542419434s
Performance | Throughput check for PGxLOD took 11.098878860473633s
Amount of data | Check the number of entities for PGxLOD took 0.12430787086486816s
Verifiability | Contribs. check for PGxLOD took 0.18753457069396973s
Interlinking | sameAs chians check for PGxLOD took 0.24171805381774902s
Interlinking | skos check for PGxLOD took 1.119832992553711s
Interlinking | skos check for PGxLOD took 0.1844949722290039s
Timeliness | dataset update frequency check for PGxLOD took 0.2715017795562744s
Currency | Creation date check for PGxLOD took 0.5831782817840576s
Currency | Modification date check for PGxLOD took 0.191603422164917s
Rep.Conc. | URIs length for PGxLOD took 2.415910005569458s
Interoperability | New vocabularies check for PGxLOD took 47.57577133178711s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.15366387367248535s
Accuracy | Check Functional Property for PGxLOD took 0.18147921562194824s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.16614389419555664s
Accuracy | Check Empty annotation labels for PGxLOD took 0.621253490447998s
Accuracy | Check White space in annotation for PGxLOD took 0.03719282150268555s
Accuracy | Check Datatype consistency for PGxLOD took 0.028900861740112305s
Consistency | Disjoint class check for PGxLOD took 0.250795841217041s
Consistency | Check Misplaced properties for PGxLOD took 2.335050344467163s
Consistency | Misplaced classes for PGxLOD took 0.31960058212280273s
Consistency | Check Ontology hijacking for PGxLOD took 1.9810242652893066s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.3652520179748535s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 3.1407477855682373s
Conciseness | Check Extensional conciseness for PGxLOD took 0.037584781646728516s
Conciseness | Check Intensional conciseness for PGxLOD took 0.32112598419189453s
Security | Sign check for PGxLOD took 0.19231510162353516s
Availability | Check URIs Dereferenciability for PGxLOD took 2652.3357017040253s
Completeness | Calculation of interlinking completeness for PGxLOD took 180.45643019676208s
Reputation | Calculation of the PageRank for PGxLOD took 0.02149510383605957s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 70.36715626716614s
Believability | Calculation of trust value for PGxLOD took 1.2874603271484375e-05s
INFO | --- Analysis for PGxLOD took 4433.160016775131s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.9456038475036621s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.39561939239501953s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02136397361755371s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0967254638671875e-05s
INFO | --- Analysis for phoible took 122.9677312374115s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 0.00010061264038085938s
Availability | VoID file availability check for Parallel ice sheet model took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.3163297176361084s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.022765398025512695s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.9087066650390625e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.2636184692382812e-05s
INFO | --- Analysis for PISM took 70.85186624526978s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 0.0001068115234375s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.3755626678466797s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.0219573974609375s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 9.34600830078125e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for planetdata-project-wiki took 1.946195125579834s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.4291374683380127s
Availability | VoID file availability check for digitized plant specimen took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 120.27488923072815s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.021112918853759766s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.82012939453125e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.0967254638671875e-05s
INFO | --- Analysis for plant-specimen took 182.97273206710815s
Availability | SPARQL endpoint availability check for Pleiades took 8.988380432128906e-05s
Availability | VoID file availability check for Pleiades took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Pleiades took 0.31543707847595215s
Reputation | Calculation of the PageRank for Pleiades took 0.02159261703491211s
Interlinking | Calculation of Degree of Connection for Pleiades took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.511543273925781e-05s
Believability | Calculation of trust value for Pleiades took 1.2636184692382812e-05s
INFO | --- Analysis for pleiades took 10.080488443374634s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 8.845329284667969e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.000762939453125s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 60.04057312011719s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.022546768188476562s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 4.601478576660156e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.049041748046875e-05s
INFO | --- Analysis for podorozhnyk took 62.128480195999146s
Availability | SPARQL endpoint availability check for Poképédia took 8.893013000488281e-05s
Availability | VoID file availability check for Poképédia took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Poképédia took 0.3299992084503174s
Reputation | Calculation of the PageRank for Poképédia took 0.02077198028564453s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.152557373046875e-05s
Believability | Calculation of trust value for Poképédia took 1.1920928955078125e-05s
INFO | --- Analysis for pokepedia-fr took 241.1240894794464s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.131431579589844e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.001177072525024414s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.3620905876159668s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.021424055099487305s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.440017700195312e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.049041748046875e-05s
INFO | --- Analysis for polymath-virtual-library took 5.601089000701904s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 8.678436279296875e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.29700779914855957s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.4809112548828125e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 1.239776611328125e-05s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 61.65183091163635s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.315376281738281e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2829468250274658s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.021155357360839844s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.314018249511719e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 1.1682510375976562e-05s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 61.52920198440552s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 9.584426879882812e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0003838539123535156s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.31095457077026367s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.021251678466796875s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 3.1948089599609375e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 1.0728836059570312e-05s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 120.76771998405457s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 0.00011086463928222656s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.29668354988098145s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.022851228713989258s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 4.6253204345703125e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 1.2159347534179688e-05s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 361.6417717933655s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 0.00011086463928222656s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.315140962600708s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.021175384521484375s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.933906555175781e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 1.2636184692382812e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 180.21176981925964s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 0.00011205673217773438s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.29429054260253906s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.02106308937072754s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.0279159545898438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 1.9550323486328125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 120.77205157279968s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 8.893013000488281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.394254207611084s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.021158933639526367s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.647804260253906e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 360.6038830280304s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 8.916854858398438e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.36646127700805664s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.022481918334960938s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.7670135498046875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 1.3113021850585938e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 61.23252844810486s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 8.702278137207031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.3086121082305908s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.02386331558227539s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 1.6592366695404053s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.3551981449127197s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 1.8691439628601074s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 0.00012731552124023438s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.3020298480987549s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.021854400634765625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.147125244140625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 1.1920928955078125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 1.786482810974121s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 0.0001270771026611328s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.2887899875640869s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.021421194076538086s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.2901763916015625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 1.3113021850585938e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 1.7426271438598633s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 8.893013000488281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 59.59063482284546s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.021054744720458984s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 3.1948089599609375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 2.3365020751953125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 420.2566120624542s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 8.630752563476562e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.30666184425354004s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.022141218185424805s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.3855438232421875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 1.33514404296875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 61.3275101184845s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 8.630752563476562e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2932279109954834s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 1.2636184692382812e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 61.73201942443848s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 0.0001087188720703125s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.31046175956726074s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.021231412887573242s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 1.3113021850585938e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 1.7142655849456787s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 8.726119995117188e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.3491091728210449s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.02170276641845703s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 1.677260398864746s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 8.749961853027344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.3825101852416992s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.021050691604614258s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 1.239776611328125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 61.75699782371521s
Availability | SPARQL endpoint availability check for prefix.cc took 0.00010561943054199219s
Availability | VoID file availability check for prefix.cc took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.36794471740722656s
Reputation | Calculation of the PageRank for prefix.cc took 0.022586584091186523s
Interlinking | Calculation of Degree of Connection for prefix.cc took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.695487976074219e-05s
Believability | Calculation of trust value for prefix.cc took 1.0967254638671875e-05s
INFO | --- Analysis for prefix-cc took 62.473978757858276s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.670046329498291s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2935302257537842s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.4345855712890625e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.71661376953125e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 66.0177948474884s
Availability | SPARQL endpoint availability check for PreLex took 5.20378851890564s
Availability | VoID file availability check for PreLex took 0.0008990764617919922s
Completeness | Calculation of interlinking completeness for PreLex took 0.33138298988342285s
Reputation | Calculation of the PageRank for PreLex took 0.02272772789001465s
Interlinking | Calculation of Degree of Connection for PreLex took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.891654968261719e-05s
Believability | Calculation of trust value for PreLex took 1.3113021850585938e-05s
INFO | --- Analysis for prelex took 12.802044868469238s
Availability | SPARQL endpoint availability check for Prelinger Archives took 3.4920573234558105s
Availability | VoID file availability check for Prelinger Archives took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 119.68396830558777s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.021976232528686523s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 4.4345855712890625e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.2874603271484375e-05s
INFO | --- Analysis for prelinger_archives took 396.5288116931915s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.29650354385375977s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0006246566772460938s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 4.142653226852417s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 0.6215226650238037s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.2972605228424072s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 2.0595836639404297s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 58.42297983169556s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.14398908615112305s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.07251548767089844s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.1544630527496338s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.1469888687133789s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.14674711227416992s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.32358264923095703s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 1.3268492221832275s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.1503736972808838s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 1.2084007263183594s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.39790821075439453s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.2171037197113037s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.15444684028625488s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.2284247875213623s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 10.778156042098999s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 0.0001227855682373047s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.14644312858581543s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.14553427696228027s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.2645416259765625s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.12416625022888184s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.14720487594604492s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 0.15508031845092773s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.15229225158691406s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 3.810243844985962s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.3694770336151123s
Accuracy | Check Functional Property for PreMOn (Predicate Model for Ontologies) took 0.19509458541870117s
Accuracy | Check Inverse Functional Property for PreMOn (Predicate Model for Ontologies) took 0.1845688819885254s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 0.9862933158874512s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08290719985961914s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.08314728736877441s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.1425480842590332s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 1.8209807872772217s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 0.39934563636779785s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.668888568878174s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.3741579055786133s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 3.048875093460083s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.1020345687866211s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.176619291305542s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.15246295928955078s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 1042.3863656520844s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.5397119522094727s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.021661996841430664s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 6.365776062011719e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 4.291534423828125e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 1.2636184692382812e-05s
INFO | --- Analysis for premon took 1165.3055005073547s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 8.726119995117188e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2950255870819092s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02084827423095703s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0008230209350585938s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 6.318092346191406e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.239776611328125e-05s
INFO | --- Analysis for princeton-library-findingaids took 62.14776349067688s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.6043975353240967s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 60.285717487335205s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.02314305305480957s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 4.696846008300781e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for PrinParLat took 362.60926723480225s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.387239933013916s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.31879401206970215s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.02144336700439453s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.940696716308594e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.4543533325195312e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 122.46906971931458s
Availability | SPARQL endpoint availability check for Prior Panel took 0.00010204315185546875s
Availability | VoID file availability check for Prior Panel took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.30582666397094727s
Reputation | Calculation of the PageRank for Prior Panel took 0.02198195457458496s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.3855438232421875e-05s
Believability | Calculation of trust value for Prior Panel took 1.1444091796875e-05s
INFO | --- Analysis for Prior_Panel took 61.16521906852722s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 0.00010085105895996094s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.29520106315612793s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.0517578125e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 1.1920928955078125e-05s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 1.9321091175079346s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 9.72747802734375e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.30835676193237305s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.02121114730834961s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.9577484130859375e-05s
Believability | Calculation of trust value for Procomún SPARQL took 1.3828277587890625e-05s
INFO | --- Analysis for procomun-sparql took 120.58021593093872s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 0.00011587142944335938s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 119.99598979949951s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.0230710506439209s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 4.220008850097656e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 1.3589859008789062e-05s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 420.6498181819916s
Availability | SPARQL endpoint availability check for ProductDB took 0.7605533599853516s
Availability | VoID file availability check for ProductDB took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for ProductDB took 0.32399797439575195s
Reputation | Calculation of the PageRank for ProductDB took 0.021778583526611328s
Interlinking | Calculation of Degree of Connection for ProductDB took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ProductDB took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for ProductDB took 9.34600830078125e-05s
Believability | Calculation of trust value for ProductDB took 1.1920928955078125e-05s
INFO | --- Analysis for productdb took 123.32820081710815s
Availability | SPARQL endpoint availability check for Product Types Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Product Types Ontology took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2839963436126709s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.022806406021118164s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.700920104980469e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for productontology took 2.8560094833374023s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 8.7738037109375e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.3071417808532715s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.021953582763671875s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010728836059570312s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.1205673217773438e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 6.064148187637329s
Availability | SPARQL endpoint availability check for provenanceweb took 40.03697752952576s
Availability | VoID file availability check for provenanceweb took 0.0008463859558105469s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.35819482803344727s
Reputation | Calculation of the PageRank for provenanceweb took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for provenanceweb took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.702278137207031e-05s
Believability | Calculation of trust value for provenanceweb took 1.33514404296875e-05s
INFO | --- Analysis for provenanceweb took 383.6593325138092s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 5.0067901611328125e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.3308713436126709s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.02366328239440918s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0011518001556396484s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00018143653869628906s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.1682510375976562e-05s
INFO | --- Analysis for proyectoapadrina took 244.4672520160675s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.72633695602417s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 60.13745331764221s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02308797836303711s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 4.1961669921875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.1682510375976562e-05s
INFO | --- Analysis for pscs-catalogue took 446.3079209327698s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 9.036064147949219e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.27271127700805664s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.0227048397064209s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.796287536621094e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.1444091796875e-05s
INFO | --- Analysis for psh-subject-headings took 61.980417251586914s
Availability | SPARQL endpoint availability check for Depression took 0.4227447509765625s
Availability | VoID file availability check for Depression took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Depression took 0.31614160537719727s
Reputation | Calculation of the PageRank for Depression took 0.02112126350402832s
Interlinking | Calculation of Degree of Connection for Depression took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Depression took 3.647804260253906e-05s
Believability | Calculation of trust value for Depression took 1.1682510375976562e-05s
INFO | --- Analysis for Psychology took 120.8348970413208s
Availability | SPARQL endpoint availability check for PubChem RDF took 9.608268737792969e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.3005390167236328s
Reputation | Calculation of the PageRank for PubChem RDF took 0.02106332778930664s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.100799560546875e-05s
Believability | Calculation of trust value for PubChem RDF took 1.1682510375976562e-05s
INFO | --- Analysis for PubChem_RDF took 123.85485291481018s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 9.942054748535156e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.368377685546875s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.02127552032470703s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0009732246398925781s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 5.078315734863281e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 1.239776611328125e-05s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 301.5860047340393s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 30.431901693344116s
Availability | VoID file availability check for Public Spending in Greece took 0.0007414817810058594s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.28740978240966797s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020815610885620117s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.678436279296875e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.3113021850585938e-05s
INFO | --- Analysis for public-spending-in-greece took 226.1250958442688s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 0.00010728836059570312s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.3145275115966797s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.021191120147705078s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 4.00543212890625e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 1.6450881958007812e-05s
INFO | --- Analysis for publications-of-charles-university-in-prague took 360.6741988658905s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.24855303764343262s
Availability | VoID file availability check for Publications Office Authority tables took 0.00037384033203125s
Extra | Recovery of all triples for Publications Office Authority tables took 198.91736769676208s
Performance | Total latancy measurement for Publications Office Authority tables took 0.577324628829956s
Amount of data | Number of triples check for Publications Office Authority tables took 69.90997886657715s
Interoperability | New terms check for Publications Office Authority tables took 53.00651741027832s
Versatility | Languages check for Publications Office Authority tables took 300.1039113998413s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 16.700531721115112s
Security | Check HTTPS for Publications Office Authority tables took 0.3165245056152344s
Interpretability | RDF structures check for Publications Office Authority tables took 0.46808815002441406s
Versatility | Serialization formats check for Publications Office Authority tables took 0.3644731044769287s
Availability | RDF dump link check for Publications Office Authority tables took 0.24791622161865234s
License | MR license check for Publications Office Authority tables took 0.42096781730651855s
License | HR license check for Publications Office Authority tables took 300.1059875488281s
Amount of data | Number of property check for Publications Office Authority tables took 0.17991065979003906s
Understandability | Number of label check for Publications Office Authority tables took 1.7623748779296875s
Understandability | URI regex check for Publications Office Authority tables took 0.35434770584106445s
Understandability | Vocabs check for Publications Office Authority tables took 0.09784317016601562s
Verifiability | Authors check for Publications Office Authority tables took 0.24607086181640625s
Verifiability | Publishers check for Publications Office Authority tables took 0.24337482452392578s
Performance | Throughput check for Publications Office Authority tables took 10.274884700775146s
Amount of data | Check the number of entities for Publications Office Authority tables took 8.749961853027344e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.13332152366638184s
Interlinking | sameAs chians check for Publications Office Authority tables took 6.5178587436676025s
Interlinking | skos check for Publications Office Authority tables took 0.459240198135376s
Interlinking | skos check for Publications Office Authority tables took 0.2716033458709717s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.24321484565734863s
Currency | Creation date check for Publications Office Authority tables took 1.2146902084350586s
Currency | Modification date check for Publications Office Authority tables took 0.13851690292358398s
Rep.Conc. | URIs length for Publications Office Authority tables took 431.9238474369049s
Interoperability | New vocabularies check for Publications Office Authority tables took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.16543102264404297s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.17884445190429688s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.15084385871887207s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 40.122493743896484s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.1170942783355713s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.7030985355377197s
Consistency | Disjoint class check for Publications Office Authority tables took 0.1461489200592041s
Consistency | Check Misplaced properties for Publications Office Authority tables took 291.8793296813965s
Consistency | Misplaced classes for Publications Office Authority tables took 8.721527814865112s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 39.11062526702881s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.743135690689087s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.5125925540924s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.2591800689697266s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.4580419063568115s
Security | Sign check for Publications Office Authority tables took 0.6883089542388916s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 13.807581901550293s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.6954574584960938s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.021918296813964844s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 0.00011396408081054688s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.9073486328125e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 1.1682510375976562e-05s
INFO | --- Analysis for publications_office_authority_tables took 9385.931663036346s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 0.00010228157043457031s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.2953197956085205s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.021720409393310547s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 4.3392181396484375e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 1.2636184692382812e-05s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 300.493381023407s
Availability | SPARQL endpoint availability check for QBOAirbase took 8.96453857421875e-05s
Availability | VoID file availability check for QBOAirbase took 0.0008957386016845703s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.3383488655090332s
Reputation | Calculation of the PageRank for QBOAirbase took 0.022928237915039062s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 8.678436279296875e-05s
Believability | Calculation of trust value for QBOAirbase took 9.298324584960938e-06s
INFO | --- Analysis for qboairbase took 195.77636790275574s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 8.392333984375e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.2905879020690918s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.026052236557006836s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0012900829315185547s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 4.76837158203125e-05s
Believability | Calculation of trust value for qualitywebdata.org took 1.3589859008789062e-05s
INFO | --- Analysis for qualitywebdata-org took 1.853489875793457s
Availability | SPARQL endpoint availability check for Qualité de l'air took 0.00010538101196289062s
Availability | VoID file availability check for Qualité de l'air took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.3309214115142822s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02145695686340332s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.147125244140625e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.049041748046875e-05s
INFO | --- Analysis for Qualité_de_l'air took 301.0473880767822s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 0.00010228157043457031s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.3500401973724365s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.025546789169311523s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0011925697326660156s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 5.8650970458984375e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.2636184692382812e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 168.91676926612854s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.6480157375335693s
Availability | VoID file availability check for Querolus in LiLa took 0.00038242340087890625s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 59.59492039680481s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.022382736206054688s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 5.0067901611328125e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for Querolus took 241.4993612766266s
Availability | SPARQL endpoint availability check for Quotations Book took 8.58306884765625e-05s
Availability | VoID file availability check for Quotations Book took 0.00031375885009765625s
Completeness | Calculation of interlinking completeness for Quotations Book took 60.068896770477295s
Reputation | Calculation of the PageRank for Quotations Book took 0.021502017974853516s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 4.00543212890625e-05s
Believability | Calculation of trust value for Quotations Book took 1.6689300537109375e-05s
INFO | --- Analysis for quotations_book took 359.9715483188629s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 60.30727434158325s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.021413326263427734s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.528594970703125e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for r4r took 121.13332653045654s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.38080430030822754s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007905960083007812s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 28.812788724899292s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7249906063079834s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.9250786304473877s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.9864554405212402s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 8.409746170043945s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.422053337097168s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15961694717407227s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1673123836517334s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13425970077514648s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14415931701660156s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14705204963684082s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15739893913269043s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15564179420471191s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.261671781539917s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13119029998779297s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14233875274658203s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13176393508911133s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.430843830108643s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.775161743164062e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1435849666595459s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15953588485717773s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1445002555847168s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14347386360168457s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15369963645935059s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13481593132019043s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2926957607269287s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 22.9629225730896s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13753676414489746s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14185833930969238s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13070034980773926s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15638279914855957s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.8623809814453125e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.217377662658691s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1342024803161621s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.006282567977905s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.9368956089019775s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.478895664215088s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.518006086349487s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.2284598350524902s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.16094684600830078s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.595676898956299s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3213019371032715s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.021488666534423828s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0009999275207519531s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.486343383789062e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.1457672119140625e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.4066696166992188e-05s
INFO | --- Analysis for racai-legalnero took 515.4471368789673s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 0.00011014938354492188s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 59.405391454696655s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.021986961364746094s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.075599670410156e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.2159347534179688e-05s
INFO | --- Analysis for racai-llod-corola-we took 61.22276830673218s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.14680719375610352s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0006799697875976562s
Extra | Recovery of all triples for PARSEME-Ro corpus took 30.60732650756836s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.7049415111541748s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.292582750320435s
Versatility | Languages check for PARSEME-Ro corpus took 16.009880304336548s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.22867751121521s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.15547657012939453s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.15592265129089355s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.15312838554382324s
License | MR license check for PARSEME-Ro corpus took 0.14274096488952637s
License | HR license check for PARSEME-Ro corpus took 10.156381607055664s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.13074088096618652s
Understandability | Number of label check for PARSEME-Ro corpus took 0.17940592765808105s
Understandability | URI regex check for PARSEME-Ro corpus took 0.3060269355773926s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.13028454780578613s
Verifiability | Authors check for PARSEME-Ro corpus took 0.14252543449401855s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.14168906211853027s
Performance | Throughput check for PARSEME-Ro corpus took 10.537740230560303s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 8.58306884765625e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.1414165496826172s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.15396881103515625s
Interlinking | skos check for PARSEME-Ro corpus took 0.14252996444702148s
Interlinking | skos check for PARSEME-Ro corpus took 0.14202666282653809s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.14182305335998535s
Currency | Creation date check for PARSEME-Ro corpus took 0.2729358673095703s
Currency | Modification date check for PARSEME-Ro corpus took 0.28270864486694336s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 79.22083449363708s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.1545405387878418s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.15241479873657227s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.13094043731689453s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 1.9191255569458008s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23272919654846191s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 4.15166449546814s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.13283920288085938s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 10.431438684463501s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 3.107659101486206s
Security | Sign check for PARSEME-Ro corpus took 0.13119173049926758s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.275434255599976s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 59.80424237251282s
