Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 5.650520324707031e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.7750873565673828s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6315639019012451s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0003497600555419922s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 8.106231689453125e-06s
INFO | --- Analysis for 0080-3626 took 8.093005657196045s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.506111145019531e-05s
Availability | VoID file availability check for 土地利用图 took 0.00033354759216308594s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.2552299499511719s
Reputation | Calculation of the PageRank for 土地利用图 took 0.019984960556030273s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.075599670410156e-05s
Believability | Calculation of trust value for 土地利用图 took 6.9141387939453125e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.7081964015960693s
Availability | SPARQL endpoint availability check for 113322 took 4.2438507080078125e-05s
Availability | VoID file availability check for 113322 took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for 113322 took 0.2554931640625s
Reputation | Calculation of the PageRank for 113322 took 0.02002263069152832s
Interlinking | Calculation of Degree of Connection for 113322 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.1948089599609375e-05s
Believability | Calculation of trust value for 113322 took 7.62939453125e-06s
INFO | --- Analysis for 11 took 4.56889271736145s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.482269287109375e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2627267837524414s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.02010512351989746s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.0040740966796875e-05s
Believability | Calculation of trust value for Korepetycje Buki took 6.9141387939453125e-06s
INFO | --- Analysis for 12323 took 2.396199941635132s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06106853485107422s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2535674571990967s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.01997828483581543s
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.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.369850158691406e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 6.9141387939453125e-06s
INFO | --- Analysis for 2000-us-census-rdf took 2.485858201980591s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.8965473175048828s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2534487247467041s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020422697067260742s
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.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.4345855712890625e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 5.245208740234375e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.00581955909729s
Availability | SPARQL endpoint availability check for Open Data Web took 0.1043391227722168s
Availability | VoID file availability check for Open Data Web took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.27948689460754395s
Reputation | Calculation of the PageRank for Open Data Web took 0.0200347900390625s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.029273986816406e-05s
Believability | Calculation of trust value for Open Data Web took 6.9141387939453125e-06s
INFO | --- Analysis for _data.odw.tw took 3.0032854080200195s
Availability | SPARQL endpoint availability check for 土地利用 took 4.458427429199219e-05s
Availability | VoID file availability check for 土地利用 took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.26895785331726074s
Reputation | Calculation of the PageRank for 土地利用 took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.9802322387695312e-05s
Believability | Calculation of trust value for 土地利用 took 7.3909759521484375e-06s
INFO | --- Analysis for _data1.odw.tw took 2.314605951309204s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.38690185546875e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.24723052978515625s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.8848648071289062e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.6927719116210938e-05s
INFO | --- Analysis for _data2.odw.tw took 4.030729055404663s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.3392181396484375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2512524127960205s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.867813110351562e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.7998106479644775s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.363059997558594e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2556583881378174s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.9087066650390625e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.0013580322265625e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 27.537195205688477s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.506111145019531e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.24287939071655273s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.218650817871094e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 8.821487426757812e-06s
INFO | --- Analysis for A1 took 2.8231048583984375s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.9544506072998047s
Availability | VoID file availability check for SummerOlympics took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2636551856994629s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 7.081031799316406e-05s
Believability | Calculation of trust value for SummerOlympics took 8.106231689453125e-06s
INFO | --- Analysis for abc took 7.098002910614014s
Availability | SPARQL endpoint availability check for Test_m took 4.315376281738281e-05s
Availability | VoID file availability check for Test_m took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Test_m took 0.2673053741455078s
Reputation | Calculation of the PageRank for Test_m took 0.02015089988708496s
Interlinking | Calculation of Degree of Connection for Test_m took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Test_m took 2.956390380859375e-05s
Believability | Calculation of trust value for Test_m took 7.62939453125e-06s
INFO | --- Analysis for ABC took 2.245959520339966s
Availability | SPARQL endpoint availability check for my intro took 4.935264587402344e-05s
Availability | VoID file availability check for my intro took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for my intro took 0.24040651321411133s
Reputation | Calculation of the PageRank for my intro took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for my intro took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for my intro took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for my intro took 3.147125244140625e-05s
Believability | Calculation of trust value for my intro took 6.67572021484375e-06s
INFO | --- Analysis for abhay_intro took 2.263906478881836s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.9081935882568359s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.2551875114440918s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00011348724365234375s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.62939453125e-06s
INFO | --- Analysis for abs-linked-data took 3.2960143089294434s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 6.67572021484375e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.2501249313354492s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.2901763916015625e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 9.059906005859375e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.851156711578369s
Availability | SPARQL endpoint availability check for AcadOnto took 4.291534423828125e-05s
Availability | VoID file availability check for AcadOnto took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.25864720344543457s
Reputation | Calculation of the PageRank for AcadOnto took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0010204315185546875s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.695487976074219e-05s
Believability | Calculation of trust value for AcadOnto took 8.106231689453125e-06s
INFO | --- Analysis for acadonto took 4.171546459197998s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.750877141952515s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.279268741607666s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.00543212890625e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.245208740234375e-06s
INFO | --- Analysis for acorn-sat took 36.359347105026245s
Availability | SPARQL endpoint availability check for Addgene took 4.410743713378906e-05s
Availability | VoID file availability check for Addgene took 0.0009348392486572266s
Completeness | Calculation of interlinking completeness for Addgene took 0.267805814743042s
Reputation | Calculation of the PageRank for Addgene took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for Addgene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.220008850097656e-05s
Believability | Calculation of trust value for Addgene took 6.9141387939453125e-06s
INFO | --- Analysis for addgene took 15.83353304862976s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.38690185546875e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.28122377395629883s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020241737365722656s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.202957153320312e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 6.67572021484375e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 4.634208917617798s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.4799363613128662s
Availability | VoID file availability check for AEMET metereological dataset took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.25706958770751953s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020155668258666992s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.4809112548828125e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 7.867813110351562e-06s
INFO | --- Analysis for aemet took 4.640252590179443s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.076957702636719e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.2812356948852539s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02022266387939453s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.075599670410156e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 6.67572021484375e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.882246971130371s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03020763397216797s
Availability | VoID file availability check for AgriNepalData took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.25901150703430176s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.985664367675781e-05s
Believability | Calculation of trust value for AgriNepalData took 6.67572021484375e-06s
INFO | --- Analysis for agrinepaldata took 2.350618600845337s
Availability | SPARQL endpoint availability check for AGRIS took 261.8872413635254s
Availability | VoID file availability check for AGRIS took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for AGRIS took 0.2739071846008301s
Reputation | Calculation of the PageRank for AGRIS took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.0108642578125e-05s
Believability | Calculation of trust value for AGRIS took 8.106231689453125e-06s
INFO | --- Analysis for agris took 557.0980439186096s
Availability | SPARQL endpoint availability check for AGROVOC took 0.2049715518951416s
Availability | VoID file availability check for AGROVOC took 0.0005559921264648438s
Extra | Recovery of all triples for AGROVOC took 30.957772970199585s
Performance | Total latancy measurement for AGROVOC took 0.45175957679748535s
Amount of data | Number of triples check for AGROVOC took 30.085137844085693s
Interoperability | New terms check for AGROVOC took 3.0493054389953613s
Versatility | Languages check for AGROVOC took 30.096884965896606s
Interpretability | Number of blank nodes check for AGROVOC took 30.088250875473022s
Interpretability | RDF structures check for AGROVOC took 0.07619881629943848s
Versatility | Serialization formats check for AGROVOC took 0.08968234062194824s
Availability | RDF dump link check for AGROVOC took 0.135483980178833s
License | MR license check for AGROVOC took 0.10304927825927734s
License | HR license check for AGROVOC took 0.5939857959747314s
Amount of data | Number of property check for AGROVOC took 0.07561254501342773s
Understandability | Number of label check for AGROVOC took 30.084208726882935s
Understandability | URI regex check for AGROVOC took 0.16753125190734863s
Understandability | Vocabs check for AGROVOC took 0.08046388626098633s
Verifiability | Authors check for AGROVOC took 0.0935964584350586s
Verifiability | Publishers check for AGROVOC took 0.09867715835571289s
Performance | Throughput check for AGROVOC took 10.526671409606934s
Amount of data | Check the number of entities for AGROVOC took 7.581710815429688e-05s
Verifiability | Contribs. check for AGROVOC took 0.07494854927062988s
Interlinking | sameAs chians check for AGROVOC took 0.08797240257263184s
Interlinking | skos check for AGROVOC took 2.9803590774536133s
Interlinking | skos check for AGROVOC took 0.1434485912322998s
Timeliness | dataset update frequency check for AGROVOC took 0.07755255699157715s
Currency | Creation date check for AGROVOC took 0.17849183082580566s
Currency | Modification date check for AGROVOC took 0.2010340690612793s
Rep.Conc. | URIs length for AGROVOC took 43.19144105911255s
Interoperability | New vocabularies check for AGROVOC took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.10043001174926758s
Accuracy | Check Empty annotation labels for AGROVOC took 17.012834787368774s
Accuracy | Check White space in annotation for AGROVOC took 3.0226938724517822s
Consistency | Disjoint class check for AGROVOC took 0.07694578170776367s
Consistency | Check Misplaced properties for AGROVOC took 12.976011514663696s
Consistency | Check Ontology hijacking for AGROVOC took 30.112058877944946s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 15.611354351043701s
Conciseness | Check Extensional conciseness for AGROVOC took 0.0001456737518310547s
Conciseness | Check Intensional conciseness for AGROVOC took 0.09219026565551758s
Security | Sign check for AGROVOC took 0.08939957618713379s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7666311264038086s
Reputation | Calculation of the PageRank for AGROVOC took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011801719665527344s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 8.106231689453125e-06s
INFO | --- Analysis for agrovoc took 368.9849486351013s
Availability | SPARQL endpoint availability check for AGROVOC took 4.172325134277344e-05s
Availability | VoID file availability check for AGROVOC took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7052896022796631s
Reputation | Calculation of the PageRank for AGROVOC took 0.020157337188720703s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.745887756347656e-05s
Believability | Calculation of trust value for AGROVOC took 7.3909759521484375e-06s
INFO | --- Analysis for agrovoc-skos took 4.67075252532959s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.632497787475586s
Availability | VoID file availability check for Analytics India Magazine took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.6904716491699219s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.019948482513427734s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.147125244140625e-05s
Believability | Calculation of trust value for Analytics India Magazine took 7.3909759521484375e-06s
INFO | --- Analysis for AIM took 8.807331800460815s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.410743713378906e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.2350304126739502s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020107746124267578s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.0517578125e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 8.344650268554688e-06s
INFO | --- Analysis for AISHE took 2.742523431777954s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.291534423828125e-05s
Availability | VoID file availability check for  equipment ontology took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.25942468643188477s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for  equipment ontology took 6.9141387939453125e-06s
INFO | --- Analysis for akash took 2.3472390174865723s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.100799560546875e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0003867149353027344s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.2628600597381592s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 2.288818359375e-05s
INFO | --- Analysis for aksworg took 2.84295654296875s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.1961669921875e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.2620248794555664s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.075599670410156e-05s
Believability | Calculation of trust value for AlchemyAPI took 7.152557373046875e-06s
INFO | --- Analysis for alchemyapi took 2.9404561519622803s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.291534423828125e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.28006839752197266s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.6716461181640625e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 8.344650268554688e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.8705079555511475s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.2028963565826416s
Availability | VoID file availability check for aliada-scanbit-net took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.2871074676513672s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.0001289844512939453s
Believability | Calculation of trust value for aliada-scanbit-net took 6.9141387939453125e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.382768392562866s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.124641418457031e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.2595663070678711s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02029132843017578s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.9087066650390625e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 1.1682510375976562e-05s
INFO | --- Analysis for allen-brain-atlas took 2.8522114753723145s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.6885519027709961s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006530284881591797s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 110.22920370101929s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7046356201171875s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.4676215648651123s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.680056571960449s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.1016364097595s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 4.026610612869263s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8983371257781982s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.5878043174743652s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6891214847564697s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5642828941345215s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5829968452453613s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 34.65637230873108s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5717940330505371s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.8172073364257812s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.106135606765747s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5664570331573486s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6634595394134521s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5894601345062256s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.767006158828735s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 0.00013566017150878906s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5462868213653564s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.579857587814331s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5804498195648193s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5625052452087402s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.714918851852417s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.1354260444641113s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1096172332763672s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 43.23412227630615s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 5.870693683624268s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5682969093322754s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6202840805053711s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.5677452087402344s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 23.451605796813965s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.047405481338501s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.6409175395965576s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.597322940826416s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 11.034760475158691s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.75325083732605s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 31.38050651550293s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3967907428741455s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 12.029989242553711s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.740633487701416s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8283941745758057s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.551560640335083s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12766.679286003113s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.6341972351074219s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.0239412784576416s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 9.417533874511719e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0013222694396972656s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.000156402587890625s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 2.1928205490112305s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 9.5367431640625e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13471.323220014572s
Availability | SPARQL endpoint availability check for Alojamientos took 4.267692565917969e-05s
Availability | VoID file availability check for Alojamientos took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.6849677562713623s
Reputation | Calculation of the PageRank for Alojamientos took 0.02063608169555664s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.1948089599609375e-05s
Believability | Calculation of trust value for Alojamientos took 7.3909759521484375e-06s
INFO | --- Analysis for alojamientos-zaragoza took 5.072928428649902s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.42502284049987793s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.24193429946899414s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.8623809814453125e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 6.198883056640625e-06s
INFO | --- Analysis for alpino-rdf took 4.287081718444824s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.2438507080078125e-05s
Availability | VoID file availability check for AAT-atawil took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.25713658332824707s
Reputation | Calculation of the PageRank for AAT-atawil took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.123283386230469e-05s
Believability | Calculation of trust value for AAT-atawil took 6.67572021484375e-06s
INFO | --- Analysis for Altawil took 2.3476808071136475s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.076957702636719e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.25908660888671875s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020845413208007812s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.218650817871094e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 7.867813110351562e-06s
INFO | --- Analysis for am-collections-online took 2.730902671813965s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.7206878662109375e-05s
Availability | VoID file availability check for Amer Nejma took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.24045395851135254s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.266334533691406e-05s
Believability | Calculation of trust value for Amer Nejma took 7.867813110351562e-06s
INFO | --- Analysis for Amer_Nejma took 2.2726423740386963s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.2559998035430908s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.170967102050781e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 8.344650268554688e-06s
INFO | --- Analysis for amon took 2.8653206825256348s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.783505916595459s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2506544589996338s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.298324584960938e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.239776611328125e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 13.806706190109253s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.2438507080078125e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.26882457733154297s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020270347595214844s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 2.9087066650390625e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 8.106231689453125e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.8932085037231445s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 7.581710815429688e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.25438761711120605s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.266334533691406e-05s
Believability | Calculation of trust value for Animal Diversity Web took 6.9141387939453125e-06s
INFO | --- Analysis for animal-diversity-web took 2.908254384994507s
Availability | SPARQL endpoint availability check for Anime Dataset took 7.295608520507812e-05s
Availability | VoID file availability check for Anime Dataset took 0.0003902912139892578s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.25764989852905273s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.314018249511719e-05s
Believability | Calculation of trust value for Anime Dataset took 7.62939453125e-06s
INFO | --- Analysis for Anime took 3.639848470687866s
Availability | SPARQL endpoint availability check for ANNO took 4.482269287109375e-05s
Availability | VoID file availability check for ANNO took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for ANNO took 0.26686763763427734s
Reputation | Calculation of the PageRank for ANNO took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for ANNO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.814697265625e-05s
Believability | Calculation of trust value for ANNO took 8.106231689453125e-06s
INFO | --- Analysis for anno took 4.307759761810303s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.315376281738281e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0010514259338378906s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2856903076171875s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 8.225440979003906e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.3589859008789062e-05s
INFO | --- Analysis for AntiqueCarsCollection took 3.1233842372894287s
Availability | SPARQL endpoint availability check for apache took 4.3392181396484375e-05s
Availability | VoID file availability check for apache took 0.0008213520050048828s
Completeness | Calculation of interlinking completeness for apache took 0.27210474014282227s
Reputation | Calculation of the PageRank for apache took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for apache took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for apache took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for apache took 5.7220458984375e-05s
Believability | Calculation of trust value for apache took 8.106231689453125e-06s
INFO | --- Analysis for apache took 3.371943235397339s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.6253204345703125e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2702326774597168s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf took 4.738080024719238s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2576749324798584s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.6108479499816895s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.25546884536743164s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020605802536010742s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.649150371551514s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0007722377777099609s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.26837801933288574s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.021532535552978516s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0010914802551269531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 6.890296936035156e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.5872581005096436s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.25882530212402344s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.5633909702301025s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2537202835083008s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02069544792175293s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.50879430770874s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.5299530029296875e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2609739303588867s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.6515796184539795s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.601478576660156e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.25789713859558105s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.487884998321533s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.26859402656555176s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 5.1975250244140625e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.642707824707031s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.649162292480469e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0011949539184570312s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.27652645111083984s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.511336088180542s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.27343106269836426s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.616241216659546s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 5.030632019042969e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0008077621459960938s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.25603604316711426s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.459785461425781e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 25.000116109848022s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.553794860839844e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.25495028495788574s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 5.533197641372681s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.25403904914855957s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.598540306091309s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 7.486343383789062e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2677271366119385s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.9114227294921875e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 9.5367431640625e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.605513572692871s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0007956027984619141s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2591211795806885s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 5.529432773590088s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.26703763008117676s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.595311403274536s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.25392651557922363s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.528953552246094s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.26319408416748047s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.516427755355835s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 5.555152893066406e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2490081787109375s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.532349348068237s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2520921230316162s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02747035026550293s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0011026859283447266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 7.152557373046875e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.577342987060547s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.28366899490356445s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.565746545791626s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 7.367134094238281e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.26629638671875s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.263458728790283s
Availability | SPARQL endpoint availability check for AragoDBPedia took 1.186863899230957s
Availability | VoID file availability check for AragoDBPedia took 0.0007081031799316406s
Extra | Recovery of all triples for AragoDBPedia took 3.5867769718170166s
Performance | Total latancy measurement for AragoDBPedia took 1.9217045307159424s
Amount of data | Number of triples check for AragoDBPedia took 0.9981927871704102s
Interoperability | New terms check for AragoDBPedia took 2.146165370941162s
Versatility | Languages check for AragoDBPedia took 60.502060890197754s
Interpretability | Number of blank nodes check for AragoDBPedia took 5.112005710601807s
Security | Check HTTPS for AragoDBPedia took 0.22949838638305664s
Interpretability | RDF structures check for AragoDBPedia took 0.806039571762085s
Versatility | Serialization formats check for AragoDBPedia took 1.1145763397216797s
Availability | RDF dump link check for AragoDBPedia took 0.38820743560791016s
License | MR license check for AragoDBPedia took 0.7625606060028076s
License | HR license check for AragoDBPedia took 8.035548210144043s
Amount of data | Number of property check for AragoDBPedia took 0.41617751121520996s
Understandability | Number of label check for AragoDBPedia took 0.6570935249328613s
Understandability | URI regex check for AragoDBPedia took 1.0427191257476807s
Understandability | Vocabs check for AragoDBPedia took 0.4693315029144287s
Verifiability | Authors check for AragoDBPedia took 0.556833028793335s
Verifiability | Publishers check for AragoDBPedia took 0.40642428398132324s
Performance | Throughput check for AragoDBPedia took 11.579101800918579s
Amount of data | Check the number of entities for AragoDBPedia took 7.796287536621094e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.53397536277771s
Interlinking | sameAs chians check for AragoDBPedia took 0.46338391304016113s
Interlinking | skos check for AragoDBPedia took 0.7049047946929932s
Interlinking | skos check for AragoDBPedia took 0.4173605442047119s
Timeliness | dataset update frequency check for AragoDBPedia took 1.15696382522583s
Currency | Creation date check for AragoDBPedia took 2.1224281787872314s
Currency | Modification date check for AragoDBPedia took 0.8982362747192383s
Rep.Conc. | URIs length for AragoDBPedia took 6.102257490158081s
Interoperability | New vocabularies check for AragoDBPedia took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.4511075019836426s
Accuracy | Check Functional Property for AragoDBPedia took 0.5740044116973877s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.542487382888794s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.3300795555114746s
Accuracy | Check White space in annotation for AragoDBPedia took 0.03023076057434082s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.029421091079711914s
Consistency | Disjoint class check for AragoDBPedia took 0.4329872131347656s
Consistency | Check Misplaced properties for AragoDBPedia took 4.801158905029297s
Consistency | Misplaced classes for AragoDBPedia took 0.6808619499206543s
Consistency | Check Ontology hijacking for AragoDBPedia took 4.0107738971710205s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3829474449157715s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.529365301132202s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.0341181755065918s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.6280803680419922s
Security | Sign check for AragoDBPedia took 0.989739179611206s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3236.4962005615234s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.7022933959960938s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.021190643310546875s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 9.465217590332031e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBPedia took 5.7220458984375e-06s
INFO | --- Analysis for aragodbpedia took 11879.869918107986s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.22483205795288s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.7033565044403076s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.0067901611328125e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for archiveshub-linkeddata took 83.81085443496704s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.601478576660156e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.2765827178955078s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.170967102050781e-05s
Believability | Calculation of trust value for Archivi ISMA took 8.58306884765625e-06s
INFO | --- Analysis for archivio-isma took 4.838918924331665s
Availability | SPARQL endpoint availability check for ARIADNE took 4.38690185546875e-05s
Availability | VoID file availability check for ARIADNE took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2628004550933838s
Reputation | Calculation of the PageRank for ARIADNE took 0.021466493606567383s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.266334533691406e-05s
Believability | Calculation of trust value for ARIADNE took 7.3909759521484375e-06s
INFO | --- Analysis for ariadne took 3.3693878650665283s
Availability | SPARQL endpoint availability check for Aristotle University took 5.412101745605469e-05s
Availability | VoID file availability check for Aristotle University took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.2432537078857422s
Reputation | Calculation of the PageRank for Aristotle University took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for Aristotle University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.0517578125e-05s
Believability | Calculation of trust value for Aristotle University took 7.867813110351562e-06s
INFO | --- Analysis for aristotle-university took 2.844569683074951s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.582302570343018s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.257765531539917s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.147125244140625e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 8.58306884765625e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 21.508112907409668s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 5.745887756347656e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.2749979496002197s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020291566848754883s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 7.152557373046875e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.883713960647583s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.953856945037842s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0003528594970703125s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.26956725120544434s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.814697265625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.059906005859375e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 17.361109972000122s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.363059997558594e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00034332275390625s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.25750017166137695s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010156631469726562s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 8.199556350708008s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 4.267692565917969e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.2472693920135498s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.2636184692382812e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 7.867813110351562e-06s
INFO | --- Analysis for Arthron took 2.26735258102417s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.315376281738281e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.25558924674987793s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010132789611816406s
Believability | Calculation of trust value for Arthroscopy community took 8.106231689453125e-06s
INFO | --- Analysis for arthroscopy took 35.44467258453369s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.7909741401672363s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.00055694580078125s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 0.08190751075744629s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 0.08177638053894043s
Versatility | Languages check for Wikidata entry for Art × Science International took 0.2581954002380371s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.08440971374511719s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.07080602645874023s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.08226966857910156s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.08351445198059082s
License | MR license check for Wikidata entry for Art × Science International took 0.09468817710876465s
License | HR license check for Wikidata entry for Art × Science International took 0.08148956298828125s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.08127427101135254s
Understandability | Number of label check for Wikidata entry for Art × Science International took 0.08646726608276367s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.1760249137878418s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.09263372421264648s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.0820455551147461s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.07559585571289062s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.00013947486877441406s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.0835411548614502s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.07009148597717285s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.08322405815124512s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.07069849967956543s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.08417224884033203s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.1648242473602295s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.15690302848815918s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 0.16964125633239746s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.09286999702453613s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.09397196769714355s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.08268952369689941s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.4536075592041016s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 0.0001595020294189453s
Security | Sign check for Wikidata entry for Art × Science International took 0.08505988121032715s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.26878952980041504s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.3589859008789062e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 4.76837158203125e-07s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 7.62939453125e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 18.234389305114746s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.4584717750549316s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2661113739013672s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0008440017700195312s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.00010919570922851562s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 12.616635799407959s
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.39620304107666s
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.0005731582641601562s
Completeness | Calculation of interlinking completeness for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.27895236015319824s
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.020644187927246094s
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.5735626220703125e-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.000957489013671875s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 9.822845458984375e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 11.078215599060059s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.4151711463928223s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2481226921081543s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.036064147949219e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 12.10207462310791s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.386554479598999s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.32901453971862793s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02109241485595703s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0009596347808837891s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.673004150390625e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-CRB took 14.438865661621094s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.396972179412842s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0003528594970703125s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2868061065673828s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.179115295410156e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 12.088574886322021s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.385160446166992s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.25574183464050293s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.743171691894531e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 5.9604644775390625e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.594050168991089s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.4200193881988525s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2668001651763916s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.416175842285156e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.706286668777466s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 7.459196329116821s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.25951290130615234s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.082389831542969e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 17.7246835231781s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.4068429470062256s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2795248031616211s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02055048942565918s
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.1682510375976562e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.53131103515625e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.571297883987427s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.3803539276123047s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.26265478134155273s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.1975250244140625e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.613620281219482s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.076178312301636s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2631227970123291s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.022353649139404297s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0008950233459472656s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.5789947509765625e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 16.198192834854126s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.390390634536743s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.25482869148254395s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02094244956970215s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.153915405273438e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.110492944717407s
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.397571563720703s
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.0006368160247802734s
Completeness | Calculation of interlinking completeness for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.25701117515563965s
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.020455360412597656s
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.049041748046875e-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.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.225440979003906e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.697743654251099s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.3859639167785645s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2771148681640625s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.38690185546875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC_-_DNB took 11.114084720611572s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.315376281738281e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.24190950393676758s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.081031799316406e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 7.152557373046875e-06s
INFO | --- Analysis for asit took 8.186213731765747s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.673004150390625e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.00035381317138671875s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2750585079193115s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020338058471679688s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.838539123535156e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.3113021850585938e-05s
INFO | --- Analysis for asjp took 4.865309953689575s
Availability | SPARQL endpoint availability check for ASN:US took 0.11392712593078613s
Availability | VoID file availability check for ASN:US took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for ASN:US took 0.23887372016906738s
Reputation | Calculation of the PageRank for ASN:US took 0.020314693450927734s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.653236389160156e-05s
Believability | Calculation of trust value for ASN:US took 5.245208740234375e-06s
INFO | --- Analysis for asn-us took 7.443985223770142s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.3392181396484375e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.3042483329772949s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.0994415283203125e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 5.245208740234375e-06s
INFO | --- Analysis for aspire-mmu took 4.636870861053467s
Availability | SPARQL endpoint availability check for associations took 4.363059997558594e-05s
Availability | VoID file availability check for associations took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for associations took 0.2824265956878662s
Reputation | Calculation of the PageRank for associations took 0.021865367889404297s
Interlinking | Calculation of Degree of Connection for associations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for associations took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for associations took 7.43865966796875e-05s
Believability | Calculation of trust value for associations took 7.152557373046875e-06s
INFO | --- Analysis for associations took 7.151787757873535s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.315376281738281e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.28139758110046387s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.9325485229492188e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 7.3909759521484375e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.8849005699157715s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 5.817413330078125e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2678565979003906s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 0.00010585784912109375s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.0728836059570312e-05s
INFO | --- Analysis for athelia-rfid took 4.064017295837402s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.172325134277344e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2695484161376953s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.8969950675964355s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.49834203720092773s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2782144546508789s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.744529724121094e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for AugustiniConfessiones took 4.0139970779418945s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5449976921081543s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.2395482063293457s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.893013000488281e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 6.67572021484375e-06s
INFO | --- Analysis for austrian_ski_racers took 3.605464220046997s
Availability | SPARQL endpoint availability check for AVsOnto took 4.291534423828125e-05s
Availability | VoID file availability check for AVsOnto took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.24556899070739746s
Reputation | Calculation of the PageRank for AVsOnto took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.0279159545898438e-05s
Believability | Calculation of trust value for AVsOnto took 6.9141387939453125e-06s
INFO | --- Analysis for AVsOnto took 3.186965227127075s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.28963518142700195s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005524158477783203s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 200.96845865249634s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4851672649383545s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06955647468567s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 234.9334716796875s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0696852207184s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.05755949020386s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2988889217376709s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22759652137756348s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15271425247192383s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09651970863342285s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 48.48832583427429s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10495233535767s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14360427856445312s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10491251945496s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.29238152503967285s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09856057167053223s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10387754440307617s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11411786079406738s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.632844686508179s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00014901161193847656s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09325623512268066s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0750801563263s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1866443157196045s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11049294471740723s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1286940574645996s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.215850830078125s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2243647575378418s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 680.5923848152161s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12235021591186523s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 30.958304166793823s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.232933759689331s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.861997127532959s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1252892017364502s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1930265426636s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 262.988018989563s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.3058316707611084s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.5479965209961s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.827867269515991s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22915410995483398s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.0160491466522217s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.644669532775879s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.430511474609375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.4373016357421875e-06s
INFO | --- Analysis for b3kat took 4520.8936858177185s
Availability | SPARQL endpoint availability check for BabelNet took 0.5205283164978027s
Availability | VoID file availability check for BabelNet took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for BabelNet took 0.7107722759246826s
Reputation | Calculation of the PageRank for BabelNet took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00016379356384277344s
Believability | Calculation of trust value for BabelNet took 1.1920928955078125e-05s
INFO | --- Analysis for babelnet took 6.502790212631226s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.1961669921875e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.286700963973999s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.6689300537109375e-05s
INFO | --- Analysis for Bacevicius.lt took 2.8840081691741943s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5358269214630127s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2837967872619629s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.02027273178100586s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.482269287109375e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 7.152557373046875e-06s
INFO | --- Analysis for bag took 4.736161708831787s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.8913412094116211s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.274702787399292s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0994415283203125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.152557373046875e-06s
INFO | --- Analysis for baixue took 3.244887113571167s
Availability | SPARQL endpoint availability check for baixue composer took 4.2438507080078125e-05s
Availability | VoID file availability check for baixue composer took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for baixue composer took 0.6938650608062744s
Reputation | Calculation of the PageRank for baixue composer took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.24249267578125e-05s
Believability | Calculation of trust value for baixue composer took 6.9141387939453125e-06s
INFO | --- Analysis for baixue_composer took 3.251980781555176s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.482269287109375e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.28243017196655273s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.170967102050781e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue_imagery took 3.225170850753784s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.5299530029296875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2584092617034912s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0517578125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.152557373046875e-06s
INFO | --- Analysis for baixue_imagery1 took 3.304781675338745s
Availability | SPARQL endpoint availability check for BAMS took 4.100799560546875e-05s
Availability | VoID file availability check for BAMS took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for BAMS took 0.24942231178283691s
Reputation | Calculation of the PageRank for BAMS took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for BAMS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.0279159545898438e-05s
Believability | Calculation of trust value for BAMS took 7.62939453125e-06s
INFO | --- Analysis for bams took 2.8518178462982178s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.678436279296875e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.26584863662719727s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 8.106231689453125e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.883906602859497s
Availability | SPARQL endpoint availability check for BBC Music took 0.37676143646240234s
Availability | VoID file availability check for BBC Music took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for BBC Music took 0.2602579593658447s
Reputation | Calculation of the PageRank for BBC Music took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001289844512939453s
Believability | Calculation of trust value for BBC Music took 1.3113021850585938e-05s
INFO | --- Analysis for bbc-music took 3.33807110786438s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.355454683303833s
Availability | VoID file availability check for BBC Programmes took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.28336071968078613s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010561943054199219s
Believability | Calculation of trust value for BBC Programmes took 7.152557373046875e-06s
INFO | --- Analysis for bbc-programmes took 13.72224497795105s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.32672858238220215s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0008037090301513672s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.25043439865112305s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00012993812561035156s
Believability | Calculation of trust value for BBC Wildlife Finder took 8.106231689453125e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.950925588607788s
Availability | SPARQL endpoint availability check for BBOP took 4.220008850097656e-05s
Availability | VoID file availability check for BBOP took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for BBOP took 0.2907876968383789s
Reputation | Calculation of the PageRank for BBOP took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for BBOP took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BBOP took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.409385681152344e-05s
Believability | Calculation of trust value for BBOP took 6.4373016357421875e-06s
INFO | --- Analysis for bbop took 2.943565845489502s
Availability | SPARQL endpoint availability check for BBOP took 4.887580871582031e-05s
Availability | VoID file availability check for BBOP took 0.0008783340454101562s
Completeness | Calculation of interlinking completeness for BBOP took 0.24915862083435059s
Reputation | Calculation of the PageRank for BBOP took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.170967102050781e-05s
Believability | Calculation of trust value for BBOP took 8.106231689453125e-06s
INFO | --- Analysis for bbop-selected took 19.866634845733643s
Availability | SPARQL endpoint availability check for Bdgp took 1.7902498245239258s
Availability | VoID file availability check for Bdgp took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2698361873626709s
Reputation | Calculation of the PageRank for Bdgp took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.170967102050781e-05s
Believability | Calculation of trust value for Bdgp took 7.62939453125e-06s
INFO | --- Analysis for bdgp took 8.494585037231445s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.315376281738281e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.2580869197845459s
Reputation | Calculation of the PageRank for Bendev Junior took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0008444786071777344s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.552436828613281e-05s
Believability | Calculation of trust value for Bendev Junior took 7.3909759521484375e-06s
INFO | --- Analysis for bendevoficial took 5.368129014968872s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.204017162322998s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.687969446182251s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.152557373046875e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.0067901611328125e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 12.123189926147461s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 5.53131103515625e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.24335336685180664s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.3855438232421875e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 7.62939453125e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.776121139526367s
Availability | SPARQL endpoint availability check for berlios took 4.291534423828125e-05s
Availability | VoID file availability check for berlios took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for berlios took 0.2511422634124756s
Reputation | Calculation of the PageRank for berlios took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for berlios took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for berlios took 8.893013000488281e-05s
Believability | Calculation of trust value for berlios took 7.62939453125e-06s
INFO | --- Analysis for berlios took 2.5026695728302s
Availability | SPARQL endpoint availability check for Between Our Worlds took 5.412101745605469e-05s
Availability | VoID file availability check for Between Our Worlds took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3420429229736328s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.2479248046875e-05s
Believability | Calculation of trust value for Between Our Worlds took 7.867813110351562e-06s
INFO | --- Analysis for betweenourworlds took 8.93012523651123s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.44925498962402344s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.2466902732849121s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.131431579589844e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for bfs-linked-data took 3.4115889072418213s
Availability | SPARQL endpoint availability check for BibBase took 0.0603334903717041s
Availability | VoID file availability check for BibBase took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for BibBase took 0.2553586959838867s
Reputation | Calculation of the PageRank for BibBase took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for BibBase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.799003601074219e-05s
Believability | Calculation of trust value for BibBase took 7.3909759521484375e-06s
INFO | --- Analysis for bibbase took 2.438356637954712s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.291534423828125e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2533104419708252s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00010061264038085938s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 8.58306884765625e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 5.531354665756226s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.220008850097656e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.25727343559265137s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010013580322265625s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 8.344650268554688e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 8.975279331207275s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 6.723403930664062e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.25075507164001465s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.8330025672912598s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.2438507080078125e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.25914692878723145s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.600120544433594e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 7.867813110351562e-06s
INFO | --- Analysis for BibSonomy took 9.504438877105713s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.3392181396484375e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.26959681510925293s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.600120544433594e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 8.344650268554688e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.031611680984497s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 5.793571472167969e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.25743889808654785s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.075599670410156e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 8.106231689453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.6429452896118164s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2795395851135254s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.877361536026001s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 2.0165770053863525s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005846023559570312s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 39.996702671051025s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5103452205657959s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 45.09508800506592s
Interoperability | New terms check for Bio2RDF::Affymetrix took 41.111271142959595s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.12762928009033s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1366715431213379s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.8221960067749023s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.2144787311553955s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 6.160666227340698s
License | MR license check for Bio2RDF::Affymetrix took 0.37207603454589844s
License | HR license check for Bio2RDF::Affymetrix took 60.09672427177429s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.13896560668945312s
Understandability | Number of label check for Bio2RDF::Affymetrix took 11.279867887496948s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.41113710403442383s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13075900077819824s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.18824458122253418s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13381457328796387s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.518528461456299s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 78.61584091186523s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.7368924617767334s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2761368751525879s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.8991677761077881s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.19349074363708496s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.11982965469360352s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.3086731433868408s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.23030567169189453s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 123.86503338813782s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 51.12646245956421s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.36969995498657227s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15950489044189453s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12305760383605957s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 19.59329080581665s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8875980377197266s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6618649959564209s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.36023783683776855s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 71.2018494606018s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.342616558074951s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 11.190859079360962s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3056297302246094s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.4403977394104s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7051334381103516s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.5796804428100586s
Security | Sign check for Bio2RDF::Affymetrix took 0.13127493858337402s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 12.858484268188477s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.8563117980957031s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020804405212402344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.608268737792969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 103.23611521720886s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 1228.8242230415344s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.6024200916290283s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006470680236816406s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 33.39566469192505s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2119519710540771s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 43.78105974197388s
Interoperability | New terms check for Bio2RDF::Biomodels took 45.60667061805725s
Versatility | Languages check for Bio2RDF::Biomodels took 60.244105100631714s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2808256149291992s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.15674901008605957s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 1.02750825881958s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.334688663482666s
Availability | RDF dump link check for Bio2RDF::Biomodels took 6.319124460220337s
License | MR license check for Bio2RDF::Biomodels took 0.5230128765106201s
License | HR license check for Bio2RDF::Biomodels took 60.24719285964966s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2657592296600342s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.519700527191162s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5840659141540527s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2714657783508301s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.28310179710388184s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.25422024726867676s
Performance | Throughput check for Bio2RDF::Biomodels took 11.212204694747925s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 78.30381274223328s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.7131674289703369s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.35981035232543945s
Interlinking | skos check for Bio2RDF::Biomodels took 1.173112392425537s
Interlinking | skos check for Bio2RDF::Biomodels took 0.33858752250671387s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.27968740463256836s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5313684940338135s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5269107818603516s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 119.29601311683655s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 72.32980513572693s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.43572330474853516s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.29393458366394043s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2759575843811035s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 18.40668225288391s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8938624858856201s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6741156578063965s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4425945281982422s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 71.68031167984009s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4663589000701904s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 12.362591981887817s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3595526218414307s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.86506128311157s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7028045654296875s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4585084915161133s
Security | Sign check for Bio2RDF::Biomodels took 0.2815713882446289s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 12.451502799987793s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 1.4080743789672852s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011897087097167969s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 45.06437945365906s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1192.157081604004s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 5.340576171875e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.2447366714477539s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 5.529910087585449s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.5845048427581787s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006852149963378906s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 34.908825397491455s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2622103691101074s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 43.97839975357056s
Interoperability | New terms check for Bio2RDF::Bioportal took 43.61859488487244s
Versatility | Languages check for Bio2RDF::Bioportal took 60.25954484939575s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.26081013679504395s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.15597820281982422s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 1.0263452529907227s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3381648063659668s
Availability | RDF dump link check for Bio2RDF::Bioportal took 6.376322984695435s
License | MR license check for Bio2RDF::Bioportal took 0.7076339721679688s
License | HR license check for Bio2RDF::Bioportal took 60.25689721107483s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.29516029357910156s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.995526790618896s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.583808183670044s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2719607353210449s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.27773094177246094s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.2922332286834717s
Performance | Throughput check for Bio2RDF::Bioportal took 11.04041075706482s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 75.02295660972595s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.2539794445037842s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3750739097595215s
Interlinking | skos check for Bio2RDF::Bioportal took 0.9326190948486328s
Interlinking | skos check for Bio2RDF::Bioportal took 0.3857126235961914s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2915940284729004s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5691406726837158s
Currency | Modification date check for Bio2RDF::Bioportal took 0.4988901615142822s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 121.67026686668396s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 103.70645308494568s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.6936168670654297s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.27299952507019043s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.28083109855651855s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 18.324336528778076s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8966672420501709s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6647086143493652s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4398469924926758s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 70.12989974021912s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4613404273986816s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 12.446197986602783s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.347421646118164s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.58018970489502s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7093276977539062s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.45029234886169434s
Security | Sign check for Bio2RDF::Bioportal took 0.25280189514160156s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 12.761178016662598s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 1.5395007133483887s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 2.8371810913085938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004203319549560547s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 50.79782724380493s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1234.4535551071167s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.14212512969970703s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.6845059394836426s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.027095556259155273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.173683166503906e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-chembl took 18.31992506980896s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.60837721824646s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006623268127441406s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 36.50828838348389s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2754263877868652s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 44.3790967464447s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 42.541099071502686s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.234392404556274s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.25556349754333496s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.1457195281982422s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 1.135012149810791s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.3360013961791992s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 6.294337034225464s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5154681205749512s
License | HR license check for Bio2RDF::Clinicaltrials took 60.247976541519165s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.2873058319091797s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.195864200592041s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5939629077911377s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2819068431854248s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2743089199066162s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.2681155204772949s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.042670249938965s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 76.3031587600708s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 2.3228158950805664s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.38854193687438965s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.957122802734375s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3493173122406006s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.27568483352661133s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5396075248718262s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5208215713500977s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 122.19372797012329s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 45.227161169052124s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4288673400878906s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2685089111328125s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.26692986488342285s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 17.876338720321655s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8893206119537354s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6552033424377441s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.45815157890319824s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 70.77494859695435s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.412213087081909s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 11.46393346786499s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3216617107391357s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.52942895889282s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7022414207458496s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.7571020126342773s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2616403102874756s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 13.967080354690552s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 1.4538648128509521s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020908832550048828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 68.69654488563538s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1189.6464459896088s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.6056339740753174s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005786418914794922s
Extra | Recovery of all triples for Bio2RDF::Ctd took 33.50401449203491s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2625901699066162s
Amount of data | Number of triples check for Bio2RDF::Ctd took 43.6413140296936s
Interoperability | New terms check for Bio2RDF::Ctd took 40.92561483383179s
Versatility | Languages check for Bio2RDF::Ctd took 60.25697875022888s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.26212573051452637s
Security | Check HTTPS for Bio2RDF::Ctd took 0.15729355812072754s
Interpretability | RDF structures check for Bio2RDF::Ctd took 1.1886038780212402s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.37328314781188965s
Availability | RDF dump link check for Bio2RDF::Ctd took 6.28227424621582s
License | MR license check for Bio2RDF::Ctd took 0.5307400226593018s
License | HR license check for Bio2RDF::Ctd took 60.249067544937134s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2993135452270508s
Understandability | Number of label check for Bio2RDF::Ctd took 9.957390069961548s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5667159557342529s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2790515422821045s
Verifiability | Authors check for Bio2RDF::Ctd took 0.2671644687652588s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.25148606300354004s
Performance | Throughput check for Bio2RDF::Ctd took 11.295020818710327s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 75.46804690361023s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.7002131938934326s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3845508098602295s
Interlinking | skos check for Bio2RDF::Ctd took 1.1801650524139404s
Interlinking | skos check for Bio2RDF::Ctd took 0.34882140159606934s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.26653528213500977s
Currency | Creation date check for Bio2RDF::Ctd took 0.530707597732544s
Currency | Modification date check for Bio2RDF::Ctd took 0.500300407409668s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 121.5520167350769s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 46.185349464416504s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.45543336868286133s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2890346050262451s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2931807041168213s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 18.744760036468506s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8864891529083252s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6530392169952393s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.4376072883605957s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 70.28923082351685s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.385354995727539s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 11.321492910385132s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3072071075439453s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.600937843322754s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6984281539916992s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.7384800910949707s
Security | Sign check for Bio2RDF::Ctd took 0.29916882514953613s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 13.192965269088745s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.8105871677398682s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.022681236267089844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 68.83169484138489s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ctd took 1188.359946012497s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.458427429199219e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.2575068473815918s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.078315734863281e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-dataset took 4.411424160003662s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.5961711406707764s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0006914138793945312s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 34.51111817359924s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.3029611110687256s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.361809492111206s
Interoperability | New terms check for Bio2RDF::Dbsnp took 42.86214232444763s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.2515811920166s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2594735622406006s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.16630244255065918s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 1.0297341346740723s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.34166979789733887s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 6.303977012634277s
License | MR license check for Bio2RDF::Dbsnp took 0.5254271030426025s
License | HR license check for Bio2RDF::Dbsnp took 60.25268840789795s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.26105809211730957s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.633196115493774s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5814073085784912s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.25907063484191895s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2929103374481201s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.27815794944763184s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.240667819976807s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 75.40702104568481s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.9011287689208984s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3755676746368408s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.9448118209838867s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.344149112701416s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2629129886627197s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5040338039398193s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5213768482208252s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 120.06554174423218s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 91.77302026748657s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4491610527038574s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2701685428619385s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.28833484649658203s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 19.99082088470459s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.884181022644043s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6781265735626221s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.4427623748779297s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 70.55549359321594s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.7370619773864746s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 11.633439540863037s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.2902889251708984s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.5127739906311s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7051236629486084s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.40237855911254883s
Security | Sign check for Bio2RDF::Dbsnp took 0.2626361846923828s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 12.162419319152832s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 1.6044340133666992s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.200241088867188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 60.83462333679199s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1221.5291585922241s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.5764763355255127s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005998611450195312s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 37.79706907272339s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2448785305023193s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 44.54157567024231s
Interoperability | New terms check for Bio2RDF::Drugbank took 43.49618983268738s
Versatility | Languages check for Bio2RDF::Drugbank took 60.254451751708984s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2638113498687744s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.1687297821044922s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 1.1729731559753418s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.33384275436401367s
Availability | RDF dump link check for Bio2RDF::Drugbank took 6.326256513595581s
License | MR license check for Bio2RDF::Drugbank took 0.5558834075927734s
License | HR license check for Bio2RDF::Drugbank took 60.250096559524536s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2702326774597168s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.457711458206177s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5862319469451904s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2735896110534668s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.27915191650390625s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.25508832931518555s
Performance | Throughput check for Bio2RDF::Drugbank took 11.447780132293701s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 73.52098846435547s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.251758337020874s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.4510817527770996s
Interlinking | skos check for Bio2RDF::Drugbank took 0.9415225982666016s
Interlinking | skos check for Bio2RDF::Drugbank took 0.351426362991333s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2761695384979248s
Currency | Creation date check for Bio2RDF::Drugbank took 0.49825215339660645s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5312933921813965s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 119.73755025863647s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 114.39051461219788s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 2.3195157051086426s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2983241081237793s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2961151599884033s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 18.21064305305481s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8843977451324463s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6497159004211426s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.4357590675354004s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 71.28654551506042s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.452793598175049s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 11.592081069946289s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3181345462799072s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.647367000579834s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7129220962524414s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.42816162109375s
Security | Sign check for Bio2RDF::Drugbank took 0.29480767250061035s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 12.680848598480225s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 1.359144926071167s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011587142944335938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 71.07101607322693s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1258.2270786762238s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 1.403045654296875s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0007193088531494141s
Extra | Recovery of all triples for Bio2RDF::Genage took 36.59122848510742s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.206559658050537s
Amount of data | Number of triples check for Bio2RDF::Genage took 45.204174757003784s
Interoperability | New terms check for Bio2RDF::Genage took 42.98865532875061s
Versatility | Languages check for Bio2RDF::Genage took 60.28228569030762s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2843947410583496s
Security | Check HTTPS for Bio2RDF::Genage took 0.14331722259521484s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.8349034786224365s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3458216190338135s
Availability | RDF dump link check for Bio2RDF::Genage took 6.258307695388794s
License | MR license check for Bio2RDF::Genage took 0.4409923553466797s
License | HR license check for Bio2RDF::Genage took 60.2455894947052s
Amount of data | Number of property check for Bio2RDF::Genage took 0.27732181549072266s
Understandability | Number of label check for Bio2RDF::Genage took 10.879490852355957s
Understandability | URI regex check for Bio2RDF::Genage took 0.5953845977783203s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2698502540588379s
Verifiability | Authors check for Bio2RDF::Genage took 0.2741861343383789s
Verifiability | Publishers check for Bio2RDF::Genage took 0.2575113773345947s
Performance | Throughput check for Bio2RDF::Genage took 10.79243803024292s
Amount of data | Check the number of entities for Bio2RDF::Genage took 74.93506288528442s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.8520548343658447s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3444943428039551s
Interlinking | skos check for Bio2RDF::Genage took 1.081974983215332s
Interlinking | skos check for Bio2RDF::Genage took 0.43000078201293945s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2714207172393799s
Currency | Creation date check for Bio2RDF::Genage took 0.525846004486084s
Currency | Modification date check for Bio2RDF::Genage took 0.5457937717437744s
Rep.Conc. | URIs length for Bio2RDF::Genage took 120.92371988296509s
Interoperability | New vocabularies check for Bio2RDF::Genage took 51.13688135147095s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4280879497528076s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2884809970855713s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2754342555999756s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 17.886925220489502s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8780186176300049s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.65244460105896s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4122288227081299s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 70.74996256828308s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.467946767807007s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 11.831824541091919s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3631024360656738s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.5935583114624s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7308204174041748s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.7146914005279541s
Security | Sign check for Bio2RDF::Genage took 0.2788045406341553s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 12.526683330535889s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 1.4370479583740234s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.03146219253540039s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0013387203216552734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 0.00010728836059570312s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 33.758955001831055s
Believability | Calculation of trust value for Bio2RDF::Genage took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-genage took 1156.6929433345795s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.25922632217407227s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.29425048828125e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-genbank took 5.1690826416015625s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.6010212898254395s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006411075592041016s
Extra | Recovery of all triples for Bio2RDF::Gendr took 36.278114557266235s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2348034381866455s
Amount of data | Number of triples check for Bio2RDF::Gendr took 43.32211494445801s
Interoperability | New terms check for Bio2RDF::Gendr took 41.93356466293335s
Versatility | Languages check for Bio2RDF::Gendr took 60.25475835800171s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2625398635864258s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1468360424041748s
Interpretability | RDF structures check for Bio2RDF::Gendr took 1.046602487564087s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.336681604385376s
Availability | RDF dump link check for Bio2RDF::Gendr took 6.289371013641357s
License | MR license check for Bio2RDF::Gendr took 0.5830543041229248s
License | HR license check for Bio2RDF::Gendr took 60.251564264297485s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.302018404006958s
Understandability | Number of label check for Bio2RDF::Gendr took 10.529703617095947s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6159515380859375s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.25012683868408203s
Verifiability | Authors check for Bio2RDF::Gendr took 0.271198034286499s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2691218852996826s
Performance | Throughput check for Bio2RDF::Gendr took 10.987961053848267s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 75.77485418319702s
Verifiability | Contribs. check for Bio2RDF::Gendr took 2.165738582611084s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3953430652618408s
Interlinking | skos check for Bio2RDF::Gendr took 0.9483509063720703s
Interlinking | skos check for Bio2RDF::Gendr took 0.3461756706237793s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2821366786956787s
Currency | Creation date check for Bio2RDF::Gendr took 0.538543701171875s
Currency | Modification date check for Bio2RDF::Gendr took 0.511782169342041s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 121.3182806968689s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 140.0737853050232s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.45607876777648926s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.28489065170288086s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2857530117034912s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 18.47700047492981s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8825008869171143s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6643033027648926s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.4078099727630615s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 69.84603452682495s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.684971332550049s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 11.333169937133789s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.328301191329956s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.54911947250366s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.708120584487915s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.456463098526001s
Security | Sign check for Bio2RDF::Gendr took 0.2772970199584961s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 12.534988164901733s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 1.486055850982666s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02093815803527832s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 7.009506225585938e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 37.95415258407593s
Believability | Calculation of trust value for Bio2RDF::Gendr took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-gendr took 1247.2002160549164s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.6096899509429932s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0009009838104248047s
Extra | Recovery of all triples for Bio2RDF::Goa took 37.00405025482178s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2251107692718506s
Amount of data | Number of triples check for Bio2RDF::Goa took 44.515822410583496s
Interoperability | New terms check for Bio2RDF::Goa took 41.821510553359985s
Versatility | Languages check for Bio2RDF::Goa took 60.258572816848755s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.2666504383087158s
Security | Check HTTPS for Bio2RDF::Goa took 0.16994762420654297s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.8720464706420898s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.35056591033935547s
Availability | RDF dump link check for Bio2RDF::Goa took 6.329784393310547s
License | MR license check for Bio2RDF::Goa took 0.5859158039093018s
License | HR license check for Bio2RDF::Goa took 60.25684857368469s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2574331760406494s
Understandability | Number of label check for Bio2RDF::Goa took 9.881389617919922s
Understandability | URI regex check for Bio2RDF::Goa took 0.571692943572998s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2754232883453369s
Verifiability | Authors check for Bio2RDF::Goa took 0.26511240005493164s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2578239440917969s
Performance | Throughput check for Bio2RDF::Goa took 11.742820739746094s
Amount of data | Check the number of entities for Bio2RDF::Goa took 72.69896078109741s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.2987027168273926s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.361081600189209s
Interlinking | skos check for Bio2RDF::Goa took 0.8373920917510986s
Interlinking | skos check for Bio2RDF::Goa took 0.3590428829193115s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.26700592041015625s
Currency | Creation date check for Bio2RDF::Goa took 0.549363374710083s
Currency | Modification date check for Bio2RDF::Goa took 0.4890284538269043s
Rep.Conc. | URIs length for Bio2RDF::Goa took 121.67427968978882s
Interoperability | New vocabularies check for Bio2RDF::Goa took 99.20372486114502s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.719210147857666s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2684152126312256s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.270371675491333s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 19.718290328979492s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8867411613464355s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6576244831085205s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.42469215393066406s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 70.47794961929321s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.479184865951538s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 11.899631023406982s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3189659118652344s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.59162187576294s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.698643684387207s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.45639467239379883s
Security | Sign check for Bio2RDF::Goa took 0.2783682346343994s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 12.23874807357788s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.9531135559082031s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020519256591796875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.556510925292969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 139.17164373397827s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-goa took 1316.510465145111s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.5941417217254639s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006527900695800781s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 34.10679292678833s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2513823509216309s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 43.56765556335449s
Interoperability | New terms check for Bio2RDF::Hgnc took 43.17284655570984s
Versatility | Languages check for Bio2RDF::Hgnc took 60.248265504837036s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2741818428039551s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.1690530776977539s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.7751927375793457s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.34108734130859375s
Availability | RDF dump link check for Bio2RDF::Hgnc took 6.402909755706787s
License | MR license check for Bio2RDF::Hgnc took 0.6109964847564697s
License | HR license check for Bio2RDF::Hgnc took 60.26635146141052s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2504434585571289s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.64647102355957s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.615328311920166s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.27341151237487793s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.27996301651000977s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.26163768768310547s
Performance | Throughput check for Bio2RDF::Hgnc took 10.88420295715332s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 75.65933299064636s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.8876316547393799s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.35820937156677246s
Interlinking | skos check for Bio2RDF::Hgnc took 0.7596840858459473s
Interlinking | skos check for Bio2RDF::Hgnc took 0.33504438400268555s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2836344242095947s
Currency | Creation date check for Bio2RDF::Hgnc took 0.4846014976501465s
Currency | Modification date check for Bio2RDF::Hgnc took 0.4969346523284912s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 121.1391806602478s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 62.419450998306274s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.42604494094848633s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.27826952934265137s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.27761149406433105s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 18.33924627304077s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8820996284484863s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6683144569396973s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4120645523071289s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 70.5465784072876s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.4326364994049072s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 11.94762921333313s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3541514873504639s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.646496057510376s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7193953990936279s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.7148339748382568s
Security | Sign check for Bio2RDF::Hgnc took 0.2938985824584961s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 12.507514953613281s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.8480284214019775s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011444091796875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 58.42900466918945s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1187.9521646499634s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.5977866649627686s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006198883056640625s
Extra | Recovery of all triples for Bio2RDF::Homologene took 34.397486448287964s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2465238571166992s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.82170915603638s
Interoperability | New terms check for Bio2RDF::Homologene took 41.32679772377014s
Versatility | Languages check for Bio2RDF::Homologene took 60.247546911239624s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.27121806144714355s
Security | Check HTTPS for Bio2RDF::Homologene took 0.15690374374389648s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.26645493507385254s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.33172607421875s
Availability | RDF dump link check for Bio2RDF::Homologene took 6.245153188705444s
License | MR license check for Bio2RDF::Homologene took 0.5326540470123291s
License | HR license check for Bio2RDF::Homologene took 60.23788237571716s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.28242921829223633s
Understandability | Number of label check for Bio2RDF::Homologene took 10.388949632644653s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6027884483337402s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.28490567207336426s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2711782455444336s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.27208924293518066s
Performance | Throughput check for Bio2RDF::Homologene took 11.321965217590332s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 76.48069667816162s
Verifiability | Contribs. check for Bio2RDF::Homologene took 2.1420586109161377s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.3842737674713135s
Interlinking | skos check for Bio2RDF::Homologene took 0.8330123424530029s
Interlinking | skos check for Bio2RDF::Homologene took 0.34462761878967285s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.2883932590484619s
Currency | Creation date check for Bio2RDF::Homologene took 0.5384695529937744s
Currency | Modification date check for Bio2RDF::Homologene took 0.5171999931335449s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 121.0448911190033s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 100.22828221321106s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4470558166503906s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.26403331756591797s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.27658653259277344s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 17.642822980880737s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8840320110321045s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6682767868041992s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4862327575683594s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 71.34192132949829s
Consistency | Misplaced classes for Bio2RDF::Homologene took 3.4771244525909424s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 11.956947565078735s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3830902576446533s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.62592172622681s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7102861404418945s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4261500835418701s
Security | Sign check for Bio2RDF::Homologene took 0.27616262435913086s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 12.149728775024414s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 1.579969882965088s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 82.06406140327454s
Believability | Calculation of trust value for Bio2RDF::Homologene took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-homologene took 1254.2463154792786s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.26758766174316406s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.021581411361694336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0009400844573974609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.981590270996094e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-inoh took 4.2563722133636475s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.5822532176971436s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006287097930908203s
Extra | Recovery of all triples for Bio2RDF::Interpro took 33.824761390686035s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2888495922088623s
Amount of data | Number of triples check for Bio2RDF::Interpro took 44.73858904838562s
Interoperability | New terms check for Bio2RDF::Interpro took 41.70289182662964s
Versatility | Languages check for Bio2RDF::Interpro took 60.243491888046265s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2597963809967041s
Security | Check HTTPS for Bio2RDF::Interpro took 0.15622258186340332s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.9181714057922363s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.32184648513793945s
Availability | RDF dump link check for Bio2RDF::Interpro took 6.3385231494903564s
License | MR license check for Bio2RDF::Interpro took 0.4929795265197754s
License | HR license check for Bio2RDF::Interpro took 60.252195835113525s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2715435028076172s
Understandability | Number of label check for Bio2RDF::Interpro took 10.14047122001648s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5787580013275146s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2645378112792969s
Verifiability | Authors check for Bio2RDF::Interpro took 0.25821495056152344s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.23977923393249512s
Performance | Throughput check for Bio2RDF::Interpro took 10.817582845687866s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 75.25168824195862s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.7078373432159424s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.36071348190307617s
Interlinking | skos check for Bio2RDF::Interpro took 0.7684237957000732s
Interlinking | skos check for Bio2RDF::Interpro took 0.3498096466064453s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2766585350036621s
Currency | Creation date check for Bio2RDF::Interpro took 0.5382080078125s
Currency | Modification date check for Bio2RDF::Interpro took 0.5601449012756348s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 122.64590501785278s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 70.11318922042847s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.40781164169311523s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.27607011795043945s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.27961015701293945s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 18.62078619003296s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8820474147796631s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.664029598236084s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.444857120513916s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 71.12032318115234s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.474215507507324s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 11.873189926147461s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3492679595947266s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 62.39393424987793s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7367329597473145s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.43998050689697266s
Security | Sign check for Bio2RDF::Interpro took 0.2752542495727539s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 13.001916885375977s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 1.341634750366211s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 35.78003811836243s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-interpro took 1181.4187214374542s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.14266157150268555s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.677828311920166s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02028679847717285s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.510185241699219e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-iproclass took 17.218591690063477s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.5889725685119629s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006237030029296875s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 34.06401324272156s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.1966946125030518s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.69542455673218s
Interoperability | New terms check for Bio2RDF::Irefindex took 41.50582242012024s
Versatility | Languages check for Bio2RDF::Irefindex took 60.25725197792053s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.27166080474853516s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.1670513153076172s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 1.0362014770507812s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3227264881134033s
Availability | RDF dump link check for Bio2RDF::Irefindex took 6.259547710418701s
License | MR license check for Bio2RDF::Irefindex took 0.6363599300384521s
License | HR license check for Bio2RDF::Irefindex took 60.243746280670166s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.28778505325317383s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.058252096176147s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5869002342224121s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.26001834869384766s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.27236390113830566s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2582416534423828s
Performance | Throughput check for Bio2RDF::Irefindex took 11.355443000793457s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 74.88116693496704s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.7924380302429199s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.37774229049682617s
Interlinking | skos check for Bio2RDF::Irefindex took 1.176814079284668s
Interlinking | skos check for Bio2RDF::Irefindex took 0.46526598930358887s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.27744579315185547s
Currency | Creation date check for Bio2RDF::Irefindex took 0.523306131362915s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5232226848602295s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 121.22071385383606s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 77.74302220344543s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4724552631378174s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2692289352416992s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.284562349319458s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 18.856299877166748s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8876426219940186s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6613874435424805s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.3790116310119629s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 70.97880578041077s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.4379115104675293s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 11.771951675415039s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3040516376495361s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.81168341636658s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7068185806274414s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4324376583099365s
Security | Sign check for Bio2RDF::Irefindex took 0.2868630886077881s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 11.808451175689697s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.9449422359466553s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020897626876831055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.368492126464844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 69.00324773788452s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1210.590446472168s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 6.842613220214844e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.7079267501831055s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.02021312713623047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.866455078125e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-kegg took 4.685333251953125s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2818164825439453s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.361701965332031e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 5.141290187835693s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.14822697639465332s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2592787742614746s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020817995071411133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.24249267578125e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.761564493179321s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.5724575519561768s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006432533264160156s
Extra | Recovery of all triples for Bio2RDF::Lsr took 35.256125688552856s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2388696670532227s
Amount of data | Number of triples check for Bio2RDF::Lsr took 43.81636095046997s
Interoperability | New terms check for Bio2RDF::Lsr took 43.22064757347107s
Versatility | Languages check for Bio2RDF::Lsr took 60.2602756023407s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.26950693130493164s
Security | Check HTTPS for Bio2RDF::Lsr took 0.15532851219177246s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.7604415416717529s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.336564302444458s
Availability | RDF dump link check for Bio2RDF::Lsr took 6.192202568054199s
License | MR license check for Bio2RDF::Lsr took 0.4394853115081787s
License | HR license check for Bio2RDF::Lsr took 60.254313468933105s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2696518898010254s
Understandability | Number of label check for Bio2RDF::Lsr took 10.352347135543823s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5931801795959473s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.2395036220550537s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2899627685546875s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.26285696029663086s
Performance | Throughput check for Bio2RDF::Lsr took 11.051679372787476s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 77.09312605857849s
Verifiability | Contribs. check for Bio2RDF::Lsr took 2.9892754554748535s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3734595775604248s
Interlinking | skos check for Bio2RDF::Lsr took 0.8393394947052002s
Interlinking | skos check for Bio2RDF::Lsr took 0.34811902046203613s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2681148052215576s
Currency | Creation date check for Bio2RDF::Lsr took 0.5257792472839355s
Currency | Modification date check for Bio2RDF::Lsr took 0.5308947563171387s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 120.8872561454773s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 88.48025703430176s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.44983530044555664s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.293438196182251s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2641572952270508s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 19.113118648529053s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.88767409324646s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6632182598114014s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.40923213958740234s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 70.61925172805786s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.691896438598633s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 11.086104154586792s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.289191484451294s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.57572269439697s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.712256908416748s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4453880786895752s
Security | Sign check for Bio2RDF::Lsr took 0.27564525604248047s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 12.123895406723022s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 1.4536628723144531s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 56.08546447753906s
Believability | Calculation of trust value for Bio2RDF::Lsr took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-lsr took 1215.4613904953003s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.5970926284790039s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0007891654968261719s
Extra | Recovery of all triples for Bio2RDF::Mesh took 34.47089409828186s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2668156623840332s
Amount of data | Number of triples check for Bio2RDF::Mesh took 43.97108864784241s
Interoperability | New terms check for Bio2RDF::Mesh took 42.60340929031372s
Versatility | Languages check for Bio2RDF::Mesh took 60.26551628112793s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.29364562034606934s
Security | Check HTTPS for Bio2RDF::Mesh took 0.1475541591644287s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.6942286491394043s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.32722973823547363s
Availability | RDF dump link check for Bio2RDF::Mesh took 6.369148015975952s
License | MR license check for Bio2RDF::Mesh took 0.49475908279418945s
License | HR license check for Bio2RDF::Mesh took 60.24069142341614s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2693636417388916s
Understandability | Number of label check for Bio2RDF::Mesh took 10.044574975967407s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5555675029754639s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2614142894744873s
Verifiability | Authors check for Bio2RDF::Mesh took 0.27879905700683594s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2645237445831299s
Performance | Throughput check for Bio2RDF::Mesh took 10.82260513305664s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 73.1866102218628s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.7047927379608154s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.36521220207214355s
Interlinking | skos check for Bio2RDF::Mesh took 1.068476676940918s
Interlinking | skos check for Bio2RDF::Mesh took 0.3485422134399414s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2828357219696045s
Currency | Creation date check for Bio2RDF::Mesh took 0.5090775489807129s
Currency | Modification date check for Bio2RDF::Mesh took 0.4898958206176758s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 121.86150240898132s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 74.79711318016052s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4231288433074951s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.27275514602661133s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.29540085792541504s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 19.268635511398315s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8854916095733643s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6546473503112793s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4354743957519531s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 70.76746320724487s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.445418119430542s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 11.751309633255005s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3153321743011475s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.973180532455444s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7218029499053955s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.4432332515716553s
Security | Sign check for Bio2RDF::Mesh took 0.27307581901550293s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 11.816426753997803s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.9304652214050293s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.867813110351562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 91.85522603988647s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-mesh took 1234.2426483631134s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.5871148109436035s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0005846023559570312s
Extra | Recovery of all triples for Bio2RDF::Mgi took 35.193065881729126s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2607109546661377s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.831331729888916s
Interoperability | New terms check for Bio2RDF::Mgi took 43.41490197181702s
Versatility | Languages check for Bio2RDF::Mgi took 60.25031542778015s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.27623891830444336s
Security | Check HTTPS for Bio2RDF::Mgi took 0.17361879348754883s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.8585691452026367s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.30257153511047363s
Availability | RDF dump link check for Bio2RDF::Mgi took 6.302478790283203s
License | MR license check for Bio2RDF::Mgi took 0.4776949882507324s
License | HR license check for Bio2RDF::Mgi took 60.24755263328552s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.3126099109649658s
Understandability | Number of label check for Bio2RDF::Mgi took 11.067628383636475s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5875904560089111s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.23789715766906738s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2741668224334717s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2701587677001953s
Performance | Throughput check for Bio2RDF::Mgi took 11.243828773498535s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 78.10960960388184s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.8484430313110352s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.37314486503601074s
Interlinking | skos check for Bio2RDF::Mgi took 0.8656656742095947s
Interlinking | skos check for Bio2RDF::Mgi took 0.3528752326965332s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.27876853942871094s
Currency | Creation date check for Bio2RDF::Mgi took 0.5114932060241699s
Currency | Modification date check for Bio2RDF::Mgi took 0.5069851875305176s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 124.19316291809082s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 67.25589680671692s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.4405202865600586s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.27112460136413574s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.3043787479400635s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 19.103932857513428s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8838715553283691s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6540658473968506s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.3946800231933594s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 70.75548696517944s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4689018726348877s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 13.197617530822754s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3601152896881104s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.89168977737427s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7350325584411621s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.43484950065612793s
Security | Sign check for Bio2RDF::Mgi took 0.2751889228820801s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 12.517683506011963s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.876838207244873s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.00011014938354492188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 108.91022849082947s
Believability | Calculation of trust value for Bio2RDF::Mgi took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-mgi took 1257.4832127094269s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.5929112434387207s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006272792816162109s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 37.22342228889465s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2562024593353271s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.71027874946594s
Interoperability | New terms check for Bio2RDF::Ncbigene took 41.8394775390625s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.24688935279846s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.26776123046875s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1569962501525879s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.8855469226837158s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.35599803924560547s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 6.282993316650391s
License | MR license check for Bio2RDF::Ncbigene took 0.5060698986053467s
License | HR license check for Bio2RDF::Ncbigene took 60.24896168708801s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2458183765411377s
Understandability | Number of label check for Bio2RDF::Ncbigene took 10.558781385421753s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5775902271270752s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.248091459274292s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.28037095069885254s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2602882385253906s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.11510944366455s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 78.99220752716064s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.27800798416137695s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3517320156097412s
Interlinking | skos check for Bio2RDF::Ncbigene took 1.0221636295318604s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.36074042320251465s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2703406810760498s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5514774322509766s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5227522850036621s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 120.02655267715454s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 57.1492395401001s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 1.5356647968292236s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2724339962005615s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.26274752616882324s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 17.844584465026855s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8762576580047607s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6889469623565674s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.4138460159301758s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 70.72624564170837s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.4481775760650635s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 11.921985149383545s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3724353313446045s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.600446939468384s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7291474342346191s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.49431705474853516s
Security | Sign check for Bio2RDF::Ncbigene took 0.2642369270324707s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 13.551537990570068s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 1.60054612159729s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012350082397460938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 81.74996399879456s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1217.5005671977997s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.5890641212463379s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0013577938079833984s
Extra | Recovery of all triples for Bio2RDF::Ndc took 34.528852701187134s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.268601655960083s
Amount of data | Number of triples check for Bio2RDF::Ndc took 43.772823095321655s
Interoperability | New terms check for Bio2RDF::Ndc took 41.61537528038025s
Versatility | Languages check for Bio2RDF::Ndc took 60.2541606426239s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.26303887367248535s
Security | Check HTTPS for Bio2RDF::Ndc took 0.17099857330322266s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.7965235710144043s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.33658361434936523s
Availability | RDF dump link check for Bio2RDF::Ndc took 6.331661224365234s
License | MR license check for Bio2RDF::Ndc took 0.508220911026001s
License | HR license check for Bio2RDF::Ndc took 60.24462127685547s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.3100395202636719s
Understandability | Number of label check for Bio2RDF::Ndc took 10.951433420181274s
Understandability | URI regex check for Bio2RDF::Ndc took 0.6095576286315918s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.24943208694458008s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2716553211212158s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2733187675476074s
Performance | Throughput check for Bio2RDF::Ndc took 11.064678192138672s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 78.75127029418945s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.8426826000213623s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.3673427104949951s
Interlinking | skos check for Bio2RDF::Ndc took 0.9164102077484131s
Interlinking | skos check for Bio2RDF::Ndc took 0.424396276473999s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.28327393531799316s
Currency | Creation date check for Bio2RDF::Ndc took 0.49479222297668457s
Currency | Modification date check for Bio2RDF::Ndc took 0.5034744739532471s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 126.30507564544678s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 127.40407586097717s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.46358489990234375s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.27692341804504395s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2701117992401123s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 18.46889615058899s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8821403980255127s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6611814498901367s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.3878164291381836s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 71.25754451751709s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.7373385429382324s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 11.129904508590698s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3150639533996582s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.60313296318054s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7220926284790039s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.434328556060791s
Security | Sign check for Bio2RDF::Ndc took 0.2774810791015625s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 12.08127212524414s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.8308925628662109s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 69.69006896018982s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-ndc took 1273.1522779464722s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.7081899642944336s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020870208740234375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-netpath took 5.554481506347656s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13149714469909668s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2649388313293457s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-nextprot took 3.7554757595062256s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.5915701389312744s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006108283996582031s
Extra | Recovery of all triples for Bio2RDF::Omim took 33.815884590148926s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2668671607971191s
Amount of data | Number of triples check for Bio2RDF::Omim took 43.77531981468201s
Interoperability | New terms check for Bio2RDF::Omim took 43.49781107902527s
Versatility | Languages check for Bio2RDF::Omim took 60.245487451553345s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.26827096939086914s
Security | Check HTTPS for Bio2RDF::Omim took 0.15602397918701172s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.8331735134124756s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.30145263671875s
Availability | RDF dump link check for Bio2RDF::Omim took 6.347131013870239s
License | MR license check for Bio2RDF::Omim took 0.4756340980529785s
License | HR license check for Bio2RDF::Omim took 60.25535798072815s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2702009677886963s
Understandability | Number of label check for Bio2RDF::Omim took 10.543091297149658s
Understandability | URI regex check for Bio2RDF::Omim took 0.5785284042358398s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2754364013671875s
Verifiability | Authors check for Bio2RDF::Omim took 0.26131582260131836s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2683696746826172s
Performance | Throughput check for Bio2RDF::Omim took 11.51626181602478s
Amount of data | Check the number of entities for Bio2RDF::Omim took 75.86389350891113s
Verifiability | Contribs. check for Bio2RDF::Omim took 2.977795124053955s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3688700199127197s
Interlinking | skos check for Bio2RDF::Omim took 0.7818603515625s
Interlinking | skos check for Bio2RDF::Omim took 0.3559610843658447s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.27887582778930664s
Currency | Creation date check for Bio2RDF::Omim took 0.5498635768890381s
Currency | Modification date check for Bio2RDF::Omim took 0.5276997089385986s
Rep.Conc. | URIs length for Bio2RDF::Omim took 121.00144791603088s
Interoperability | New vocabularies check for Bio2RDF::Omim took 106.48722243309021s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4216172695159912s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.26873087882995605s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2667417526245117s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 18.273521184921265s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8802931308746338s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6613988876342773s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.42572760581970215s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 71.25647783279419s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.7012887001037598s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 11.675421476364136s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.300234079360962s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.53717803955078s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7109997272491455s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.42235898971557617s
Security | Sign check for Bio2RDF::Omim took 0.26933884620666504s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 13.80808138847351s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.49786949157714844s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013899803161621094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 120.97620248794556s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-omim took 1297.6908543109894s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 5.4836273193359375e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.7488985061645508s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.220008850097656e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 4.50417160987854s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.5948910713195801s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0005826950073242188s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 34.87694787979126s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2780911922454834s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 44.05834746360779s
Interoperability | New terms check for Bio2RDF::Orphanet took 42.66982626914978s
Versatility | Languages check for Bio2RDF::Orphanet took 60.236149311065674s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.26009035110473633s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15594100952148438s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.8489482402801514s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.3358950614929199s
Availability | RDF dump link check for Bio2RDF::Orphanet took 6.327301263809204s
License | MR license check for Bio2RDF::Orphanet took 0.43637824058532715s
License | HR license check for Bio2RDF::Orphanet took 60.23336744308472s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.26727890968322754s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.14155912399292s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5489411354064941s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2575664520263672s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.27791619300842285s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.25049567222595215s
Performance | Throughput check for Bio2RDF::Orphanet took 11.932076692581177s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 74.54460620880127s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.7241952419281006s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.3825654983520508s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7190790176391602s
Interlinking | skos check for Bio2RDF::Orphanet took 0.34677958488464355s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2725799083709717s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5067965984344482s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5237185955047607s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 118.12434792518616s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 56.138906717300415s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4479100704193115s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2802755832672119s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2931082248687744s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 17.203206539154053s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8818521499633789s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6753964424133301s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.46900081634521484s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 70.85235261917114s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.4935874938964844s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 11.80303168296814s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3002567291259766s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.56154251098633s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7188854217529297s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.7078006267547607s
Security | Sign check for Bio2RDF::Orphanet took 0.2664825916290283s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 11.821670532226562s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.5082569122314453s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.43865966796875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 59.96654987335205s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1186.917194366455s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.951540470123291s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.00035262107849121094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2944302558898926s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 11.182219743728638s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.5963430404663086s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006577968597412109s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 37.317548990249634s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2408463954925537s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.30551218986511s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 40.927250146865845s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.239994764328s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.26880335807800293s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16763520240783691s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 1.0262598991394043s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.33353424072265625s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 6.3787925243377686s
License | MR license check for Bio2RDF::Pharmgkb took 0.4952569007873535s
License | HR license check for Bio2RDF::Pharmgkb took 60.25814080238342s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.3125190734863281s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.206514835357666s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.6160409450531006s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.24317193031311035s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.27005457878112793s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.26440978050231934s
Performance | Throughput check for Bio2RDF::Pharmgkb took 10.947693109512329s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 75.41750240325928s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 1.2327301502227783s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.3443715572357178s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.8342657089233398s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3486032485961914s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2903130054473877s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5042769908905029s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.4871635437011719s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 120.14222288131714s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 166.15020418167114s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.47475647926330566s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.26665353775024414s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.26618432998657227s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 18.301918029785156s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.883063554763794s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.7030913829803467s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.7491843700408936s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 70.32108616828918s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4420511722564697s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 12.247516870498657s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.327453851699829s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.54553151130676s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.716843843460083s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.46311497688293457s
Security | Sign check for Bio2RDF::Pharmgkb took 0.28789234161376953s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 11.483709335327148s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.3752429485321045s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 59.106905698776245s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1297.8128542900085s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.601478576660156e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2725796699523926s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.647101879119873s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.2726705074310303s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pid took 4.239217758178711s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 6.699562072753906e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.24680471420288086s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.761429786682129s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.576207160949707s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0012516975402832031s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 35.68169808387756s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2866418361663818s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.480473041534424s
Interoperability | New terms check for Bio2RDF::Pubmed took 43.39962458610535s
Versatility | Languages check for Bio2RDF::Pubmed took 60.256038188934326s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2744579315185547s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15634703636169434s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.271104097366333s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.34713101387023926s
Availability | RDF dump link check for Bio2RDF::Pubmed took 6.301160097122192s
License | MR license check for Bio2RDF::Pubmed took 0.45136165618896484s
License | HR license check for Bio2RDF::Pubmed took 60.25519895553589s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2588484287261963s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.173310041427612s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5610237121582031s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2713901996612549s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2620372772216797s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.6037344932556152s
Performance | Throughput check for Bio2RDF::Pubmed took 11.231039047241211s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 74.77367162704468s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 2.190751552581787s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.37218570709228516s
Interlinking | skos check for Bio2RDF::Pubmed took 0.8378133773803711s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3684523105621338s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2780179977416992s
Currency | Creation date check for Bio2RDF::Pubmed took 0.515545129776001s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5333328247070312s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 122.56467151641846s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 61.13274645805359s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.42455363273620605s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.28751063346862793s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.27472829818725586s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 17.931681871414185s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8817150592803955s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6748638153076172s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.42298030853271484s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 70.60204339027405s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.433579921722412s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 11.933868646621704s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.336916446685791s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.51929688453674s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.702235221862793s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.7082781791687012s
Security | Sign check for Bio2RDF::Pubmed took 0.26512908935546875s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 12.182857751846313s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.8146412372589111s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013828277587890625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 106.87908387184143s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1239.8982245922089s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.2663552761077881s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.534027099609375e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-reactome took 5.060804605484009s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.725379467010498s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.3882598876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.3981094360351562s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.14173269271850586s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0013577938079833984s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.2919487953186035s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0010056495666503906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.344650268554688e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sabiork took 9.305064916610718s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.5863234996795654s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006878376007080078s
Extra | Recovery of all triples for Bio2RDF::Sgd took 35.720900774002075s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.24680495262146s
Amount of data | Number of triples check for Bio2RDF::Sgd took 43.928361892700195s
Interoperability | New terms check for Bio2RDF::Sgd took 45.503729820251465s
Versatility | Languages check for Bio2RDF::Sgd took 60.23943614959717s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2835564613342285s
Security | Check HTTPS for Bio2RDF::Sgd took 0.155012845993042s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.8886234760284424s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.3312647342681885s
Availability | RDF dump link check for Bio2RDF::Sgd took 6.272172689437866s
License | MR license check for Bio2RDF::Sgd took 0.44780850410461426s
License | HR license check for Bio2RDF::Sgd took 60.25437784194946s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.29302430152893066s
Understandability | Number of label check for Bio2RDF::Sgd took 10.183274030685425s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5589170455932617s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2760806083679199s
Verifiability | Authors check for Bio2RDF::Sgd took 0.26514577865600586s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.24250578880310059s
Performance | Throughput check for Bio2RDF::Sgd took 10.555472135543823s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 75.05262184143066s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.6832489967346191s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3387172222137451s
Interlinking | skos check for Bio2RDF::Sgd took 0.7481303215026855s
Interlinking | skos check for Bio2RDF::Sgd took 0.34185242652893066s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.28090357780456543s
Currency | Creation date check for Bio2RDF::Sgd took 0.511589527130127s
Currency | Modification date check for Bio2RDF::Sgd took 0.5450317859649658s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 120.53865432739258s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 73.5311861038208s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.47565746307373047s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2876560688018799s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.27215147018432617s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 18.20844578742981s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.879772424697876s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6600103378295898s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.41152119636535645s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 71.36766290664673s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4344069957733154s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 11.352615356445312s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3256950378417969s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.82359862327576s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7106838226318359s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4641537666320801s
Security | Sign check for Bio2RDF::Sgd took 0.2788980007171631s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 11.975984573364258s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 1.0741550922393799s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011491775512695312s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 71.27444219589233s
Believability | Calculation of trust value for Bio2RDF::Sgd took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-sgd took 1211.4439675807953s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.5299530029296875e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.2581651210784912s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02007913589477539s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.719329833984375e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 4.050046682357788s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 1.386258602142334s
Availability | VoID file availability check for Bio2RDF::Sider took 0.00030112266540527344s
Extra | Recovery of all triples for Bio2RDF::Sider took 34.607969999313354s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2784366607666016s
Amount of data | Number of triples check for Bio2RDF::Sider took 43.82011938095093s
Interoperability | New terms check for Bio2RDF::Sider took 41.26139235496521s
Versatility | Languages check for Bio2RDF::Sider took 60.24025917053223s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.26718759536743164s
Security | Check HTTPS for Bio2RDF::Sider took 0.16681241989135742s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.8030693531036377s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3546617031097412s
Availability | RDF dump link check for Bio2RDF::Sider took 6.401386976242065s
License | MR license check for Bio2RDF::Sider took 0.5980648994445801s
License | HR license check for Bio2RDF::Sider took 60.24938702583313s
Amount of data | Number of property check for Bio2RDF::Sider took 0.2858004570007324s
Understandability | Number of label check for Bio2RDF::Sider took 10.649004459381104s
Understandability | URI regex check for Bio2RDF::Sider took 0.5998470783233643s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2594575881958008s
Verifiability | Authors check for Bio2RDF::Sider took 0.279421329498291s
Verifiability | Publishers check for Bio2RDF::Sider took 0.25458312034606934s
Performance | Throughput check for Bio2RDF::Sider took 11.652952432632446s
Amount of data | Check the number of entities for Bio2RDF::Sider took 75.33937668800354s
Verifiability | Contribs. check for Bio2RDF::Sider took 1.6605753898620605s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3776206970214844s
Interlinking | skos check for Bio2RDF::Sider took 0.911395788192749s
Interlinking | skos check for Bio2RDF::Sider took 0.3425719738006592s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.26941967010498047s
Currency | Creation date check for Bio2RDF::Sider took 0.5284843444824219s
Currency | Modification date check for Bio2RDF::Sider took 0.5177421569824219s
Rep.Conc. | URIs length for Bio2RDF::Sider took 119.88667583465576s
Interoperability | New vocabularies check for Bio2RDF::Sider took 171.71681356430054s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.40676069259643555s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.27965593338012695s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.26933765411376953s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 18.830331802368164s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8925647735595703s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6630215644836426s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.7484116554260254s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 69.99303603172302s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.485509157180786s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 11.885754585266113s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3016891479492188s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.55540156364441s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.711773157119751s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4501349925994873s
Security | Sign check for Bio2RDF::Sider took 0.26937437057495117s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 17.60654640197754s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.8732883930206299s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.6716461181640625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 100.1672728061676s
Believability | Calculation of trust value for Bio2RDF::Sider took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sider took 1349.3298380374908s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.26804351806640625s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-spike took 4.130451917648315s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 5.340576171875e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.281536340713501s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.38690185546875e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-taxon took 3.049546718597412s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.5738124847412109s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0005891323089599609s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 37.51550650596619s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2413854598999023s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 44.47649812698364s
Interoperability | New terms check for Bio2RDF::Taxonomy took 41.863529443740845s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.25177073478699s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2715442180633545s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.16156840324401855s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.781259298324585s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3422107696533203s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 6.232993125915527s
License | MR license check for Bio2RDF::Taxonomy took 0.4899628162384033s
License | HR license check for Bio2RDF::Taxonomy took 60.24595832824707s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2635204792022705s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.658560276031494s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6140923500061035s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2532618045806885s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.2611396312713623s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.268993616104126s
Performance | Throughput check for Bio2RDF::Taxonomy took 10.864559173583984s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 77.33572149276733s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 2.3087637424468994s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3801720142364502s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.8944447040557861s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3473072052001953s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2509315013885498s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5175724029541016s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5106253623962402s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 119.05420207977295s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 50.584365367889404s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.412930965423584s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.29404568672180176s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.28011560440063477s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 18.69814443588257s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8871722221374512s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6685504913330078s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.4805755615234375s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 70.71099472045898s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.447916030883789s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 12.116745233535767s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.2893176078796387s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.527018785476685s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7036430835723877s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 1.8997466564178467s
Security | Sign check for Bio2RDF::Taxonomy took 0.27071499824523926s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 11.967611074447632s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.4200313091278076s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 54.08677649497986s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1180.4722459316254s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.16494107246398926s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.6937355995178223s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 17.353716373443604s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.5729913711547852s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006933212280273438s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 35.68124580383301s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2544186115264893s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 44.146241903305054s
Interoperability | New terms check for Bio2RDF::Wormbase took 44.50849390029907s
Versatility | Languages check for Bio2RDF::Wormbase took 60.249123096466064s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.26465678215026855s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15679144859313965s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.9963843822479248s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.34167981147766113s
Availability | RDF dump link check for Bio2RDF::Wormbase took 6.312113523483276s
License | MR license check for Bio2RDF::Wormbase took 0.4310421943664551s
License | HR license check for Bio2RDF::Wormbase took 60.246824979782104s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.29895877838134766s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.364954710006714s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6292257308959961s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.27550458908081055s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2636911869049072s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.25040388107299805s
Performance | Throughput check for Bio2RDF::Wormbase took 11.77498722076416s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 78.63510608673096s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.25715017318725586s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.36144375801086426s
Interlinking | skos check for Bio2RDF::Wormbase took 1.0391695499420166s
Interlinking | skos check for Bio2RDF::Wormbase took 0.3496572971343994s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2614402770996094s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5385053157806396s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5144917964935303s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 121.02154278755188s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 82.50782060623169s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.7314071655273438s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.30777859687805176s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2751779556274414s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 19.142537593841553s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.9039628505706787s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6601109504699707s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.45490550994873047s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 71.44571089744568s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.4386987686157227s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 11.30650782585144s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3077304363250732s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.59848737716675s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7212479114532471s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4322841167449951s
Security | Sign check for Bio2RDF::Wormbase took 0.2795746326446533s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 11.93233323097229s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 1.0054452419281006s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.988380432128906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 72.90116596221924s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1231.6027162075043s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.458427429199219e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.686046838760376s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.02003335952758789s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.2159347534179688e-05s
Believability | Calculation of trust value for Biografías y Vidas took 6.9141387939453125e-06s
INFO | --- Analysis for biografiasyvidas took 4.043095350265503s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.2793610095977783s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.7200841903686523s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.511543273925781e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 5.0067901611328125e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 4.006630182266235s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.295608520507812e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.2903003692626953s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.02086019515991211s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.2901763916015625e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for biolit took 4.306117057800293s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.458427429199219e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0003819465637207031s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.2941417694091797s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.021376848220825195s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0013456344604492188s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 5.650520324707031e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 8.106231689453125e-06s
INFO | --- Analysis for biolod-pdb took 8.515445232391357s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6249287128448486s
Availability | VoID file availability check for BioModels RDF took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2693521976470947s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.814697265625e-05s
Believability | Calculation of trust value for BioModels RDF took 1.1920928955078125e-05s
INFO | --- Analysis for biomodels-rdf took 3.7882821559906006s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.8911898136138916s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2724885940551758s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02112722396850586s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.266334533691406e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.821487426757812e-06s
INFO | --- Analysis for Biop took 7.594509124755859s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.792213439941406e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26746416091918945s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0008988380432128906s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.1484832763671875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.344650268554688e-06s
INFO | --- Analysis for Bioportal took 2.4364664554595947s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.1961669921875e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2568645477294922s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006349086761474609s
Believability | Calculation of trust value for Amphibian gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-aao took 2.764012336730957s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.1961669921875e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2663686275482178s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00030303001403808594s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-aba took 2.601166248321533s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2616119384765625s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015485286712646484s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-acgt took 2.548943281173706s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.220008850097656e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0003800392150878906s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.23250246047973633s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003323554992675781s
Believability | Calculation of trust value for Animal natural history and life history took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-adw took 3.398918867111206s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.26962947845458984s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004677772521972656s
Believability | Calculation of trust value for Anatomical Entity Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-aeo took 2.6052985191345215s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.25195741653442383s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0009329319000244141s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0010993480682373047s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-aero took 2.538984537124634s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.410743713378906e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2584564685821533s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00044989585876464844s
Believability | Calculation of trust value for AI/RHEUM took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-air took 2.5524110794067383s
Availability | SPARQL endpoint availability check for Amino Acid took 4.38690185546875e-05s
Availability | VoID file availability check for Amino Acid took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.26601171493530273s
Reputation | Calculation of the PageRank for Amino Acid took 0.021135330200195312s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002713203430175781s
Believability | Calculation of trust value for Amino Acid took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.7308130264282227s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 5.7697296142578125e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.275254487991333s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.02120494842529297s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0003018379211425781s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-apo took 2.611602306365967s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.315376281738281e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2744934558868408s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.022099018096923828s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0011603832244873047s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00031828880310058594s
Believability | Calculation of trust value for African Traditional Medicine took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-atmo took 2.656477451324463s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.315376281738281e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2554135322570801s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.021074533462524414s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.465217590332031e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ato took 2.52933931350708s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.25911903381347656s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.001363515853881836s
Believability | Calculation of trust value for BioAssay Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-bao took 2.574256420135498s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 5.555152893066406e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.25226402282714844s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00040268898010253906s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.58156681060791s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 5.698204040527344e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2656710147857666s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003402233123779297s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bcgo took 2.588259696960449s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 5.221366882324219e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.24406647682189941s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014255046844482422s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-bdo took 2.548018217086792s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 7.43865966796875e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.23816347122192383s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.02085733413696289s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.000530242919921875s
Believability | Calculation of trust value for Basic Formal Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bfo took 2.625483989715576s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.696846008300781e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2690141201019287s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007545948028564453s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bho took 2.593007802963257s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.270127534866333s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004849433898925781s
Believability | Calculation of trust value for Bilateria anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bila took 2.5741374492645264s
Availability | SPARQL endpoint availability check for BIRNLex took 5.507469177246094e-05s
Availability | VoID file availability check for BIRNLex took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.25602221488952637s
Reputation | Calculation of the PageRank for BIRNLex took 0.021382808685302734s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.001108407974243164s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0016789436340332031s
Believability | Calculation of trust value for BIRNLex took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-birnlex took 2.5218136310577393s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2672278881072998s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007948875427246094s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.61181378364563s
Availability | SPARQL endpoint availability check for BioPAX took 4.267692565917969e-05s
Availability | VoID file availability check for BioPAX took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for BioPAX took 0.26755285263061523s
Reputation | Calculation of the PageRank for BioPAX took 0.021030426025390625s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00010609626770019531s
Believability | Calculation of trust value for BioPAX took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bp took 2.6648449897766113s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.28035497665405273s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020270347595214844s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003440380096435547s
Believability | Calculation of trust value for Biomedical Resource Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.6347243785858154s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.2595047950744629s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020833969116210938s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00022172927856445312s
Believability | Calculation of trust value for Spatial Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-bspo took 2.6033451557159424s
Availability | SPARQL endpoint availability check for BioTop took 4.38690185546875e-05s
Availability | VoID file availability check for BioTop took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for BioTop took 0.25989842414855957s
Reputation | Calculation of the PageRank for BioTop took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for BioTop took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006842613220214844s
Believability | Calculation of trust value for BioTop took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bt took 2.516042947769165s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.553794860839844e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.28372979164123535s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.1444091796875e-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.0009007453918457031s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bto took 2.6616313457489014s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.30251121520996094s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.0211031436920166s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0009520053863525391s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0019986629486083984s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-canco took 3.042853355407715s
Availability | SPARQL endpoint availability check for CAO took 4.38690185546875e-05s
Availability | VoID file availability check for CAO took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for CAO took 0.2914426326751709s
Reputation | Calculation of the PageRank for CAO took 0.02028369903564453s
Interlinking | Calculation of Degree of Connection for CAO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CAO took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006072521209716797s
Believability | Calculation of trust value for CAO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cao took 2.5955018997192383s
Availability | SPARQL endpoint availability check for CareLex took 4.2438507080078125e-05s
Availability | VoID file availability check for CareLex took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for CareLex took 0.2682478427886963s
Reputation | Calculation of the PageRank for CareLex took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.078315734863281e-05s
Believability | Calculation of trust value for CareLex took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-carelex took 2.56266713142395s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2624828815460205s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.021787405014038086s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0011098384857177734s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0009198188781738281s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cco took 2.6301043033599854s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.29073214530944824s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025534629821777344s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cdao took 2.6140193939208984s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.38690185546875e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2516615390777588s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.000985860824584961s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008993148803710938s
Believability | Calculation of trust value for Chemical entities of biological interest took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-chebi took 2.6242475509643555s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 5.555152893066406e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.256152868270874s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00026154518127441406s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.5580685138702393s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.2562880516052246s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007772445678710938s
Believability | Calculation of trust value for Chemical Information Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cheminf took 2.649324417114258s
Availability | SPARQL endpoint availability check for Cell type took 4.1484832763671875e-05s
Availability | VoID file availability check for Cell type took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Cell type took 0.2473583221435547s
Reputation | Calculation of the PageRank for Cell type took 0.02027726173400879s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00039196014404296875s
Believability | Calculation of trust value for Cell type took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cl took 2.4925596714019775s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.28159141540527344s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008318424224853516s
Believability | Calculation of trust value for Cell Line Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-clo took 2.5530059337615967s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.25001096725463867s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020890235900878906s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001804828643798828s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cmo took 2.621180295944214s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.25734853744506836s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020170211791992188s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cno took 2.595201253890991s
Availability | SPARQL endpoint availability check for Wheat trait took 4.1961669921875e-05s
Availability | VoID file availability check for Wheat trait took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.25309252738952637s
Reputation | Calculation of the PageRank for Wheat trait took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for Wheat trait took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.173683166503906e-05s
Believability | Calculation of trust value for Wheat trait took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.5669331550598145s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.3392181396484375e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.2690896987915039s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00035858154296875s
Believability | Calculation of trust value for Cognitive Atlas took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cogat took 2.6261744499206543s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.26769042015075684s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.000736236572265625s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cogpo took 2.620492935180664s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 7.343292236328125e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2507810592651367s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00043463706970214844s
Believability | Calculation of trust value for Current Procedural Terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cpt took 2.577561855316162s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 6.794929504394531e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3074464797973633s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020900487899780273s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0019063949584960938s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-csp took 3.0975286960601807s
Availability | SPARQL endpoint availability check for COSTART took 9.5367431640625e-05s
Availability | VoID file availability check for COSTART took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for COSTART took 0.24474382400512695s
Reputation | Calculation of the PageRank for COSTART took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for COSTART took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COSTART took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.00103759765625s
Believability | Calculation of trust value for COSTART took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cst took 2.571758508682251s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.291534423828125e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.27522969245910645s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005242824554443359s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ctcae took 2.591627836227417s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 5.269050598144531e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.28342509269714355s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004918575286865234s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ctx took 2.6132113933563232s
Availability | SPARQL endpoint availability check for Dendritic cell took 5.841255187988281e-05s
Availability | VoID file availability check for Dendritic cell took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.28177380561828613s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0003421306610107422s
Believability | Calculation of trust value for Dendritic cell took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.6056015491485596s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2587277889251709s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.369850158691406e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ddanat took 2.5912861824035645s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.26125359535217285s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.00098419189453125s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ddi took 2.5777230262756348s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 9.870529174804688e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2855079174041748s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.797645568847656e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.5989606380462646s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.28609728813171387s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001590251922607422s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.5637025833129883s
Availability | SPARQL endpoint availability check for Human disease ontology took 6.651878356933594e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2592658996582031s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02079153060913086s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006563663482666016s
Believability | Calculation of trust value for Human disease ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-doid took 2.6517796516418457s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2584073543548584s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.021987199783325195s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008268356323242188s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ecg took 2.630917549133301s
Availability | SPARQL endpoint availability check for Evidence codes took 0.00010156631469726562s
Availability | VoID file availability check for Evidence codes took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2695424556732178s
Reputation | Calculation of the PageRank for Evidence codes took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.218650817871094e-05s
Believability | Calculation of trust value for Evidence codes took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-eco took 2.600428581237793s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3206460475921631s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017476081848144531s
Believability | Calculation of trust value for Experimental Factor Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-efo took 2.9837160110473633s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.3392181396484375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.26683735847473145s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011990070343017578s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ehda took 2.587686777114868s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.291534423828125e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.2737569808959961s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007691383361816406s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.5423004627227783s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.267692565917969e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.25485944747924805s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005290508270263672s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.5365195274353027s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.2438507080078125e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2621290683746338s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.0279159545898438e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-emap took 2.5731546878814697s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2546231746673584s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0004181861877441406s
Believability | Calculation of trust value for Environment Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-envo took 2.4818906784057617s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.315376281738281e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.25115060806274414s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0008318424224853516s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00033664703369140625s
Believability | Calculation of trust value for Plant environmental conditions took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-eo took 2.5478012561798096s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.26674509048461914s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012192726135253906s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ep took 2.7654526233673096s
Availability | SPARQL endpoint availability check for Epilepsy took 4.2438507080078125e-05s
Availability | VoID file availability check for Epilepsy took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2532944679260254s
Reputation | Calculation of the PageRank for Epilepsy took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001308917999267578s
Believability | Calculation of trust value for Epilepsy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.540969133377075s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.291534423828125e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.26361727714538574s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020221948623657227s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.00119781494140625s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ero took 2.493335485458374s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.410743713378906e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.26845645904541016s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.001157999038696289s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ev took 2.567115068435669s
Availability | SPARQL endpoint availability check for ExO took 4.4345855712890625e-05s
Availability | VoID file availability check for ExO took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for ExO took 0.254241943359375s
Reputation | Calculation of the PageRank for ExO took 0.020815372467041016s
Interlinking | Calculation of Degree of Connection for ExO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ExO took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for ExO took 0.000263214111328125s
Believability | Calculation of trust value for ExO took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-exo took 2.535989761352539s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 5.030632019042969e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.26527833938598633s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011420249938964844s
Believability | Calculation of trust value for Fungal gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fao took 2.5803442001342773s
Availability | SPARQL endpoint availability check for Biological imaging methods took 5.6743621826171875e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2432718276977539s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00019788742065429688s
Believability | Calculation of trust value for Biological imaging methods took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fbbi took 2.5680737495422363s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.26050329208374023s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006835460662841797s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbbt took 2.609856367111206s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 5.030632019042969e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.24473357200622559s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00041794776916503906s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbcv took 2.591834306716919s
Availability | SPARQL endpoint availability check for Drosophila development took 9.179115295410156e-05s
Availability | VoID file availability check for Drosophila development took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2633039951324463s
Reputation | Calculation of the PageRank for Drosophila development took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.863739013671875e-05s
Believability | Calculation of trust value for Drosophila development took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fbdv took 2.6868131160736084s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.27182579040527344s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003833770751953125s
Believability | Calculation of trust value for Fly taxonomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbsp took 2.6063072681427s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 5.3882598876953125e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.26743483543395996s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022792816162109375s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.619227647781372s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.24591398239135742s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004127025604248047s
Believability | Calculation of trust value for Family Health History Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fhho took 2.575983762741089s
Availability | SPARQL endpoint availability check for Influenza Ontology took 8.225440979003906e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.2575836181640625s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.022275686264038086s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010592937469482422s
Believability | Calculation of trust value for Influenza Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-flu took 2.509488582611084s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.24523544311523438s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.246566772460938e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fma took 2.5834832191467285s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2569565773010254s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00013017654418945312s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fypo took 2.5324761867523193s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.76837158203125e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.25820446014404297s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.036064147949219e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-geospecies took 2.58119535446167s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for General Formal Ontology took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2563610076904297s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016641616821289062s
Believability | Calculation of trust value for General Formal Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gfo took 2.6457316875457764s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 5.7697296142578125e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2508862018585205s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006031990051269531s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.5695078372955322s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.267692565917969e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2628028392791748s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008749961853027344s
Believability | Calculation of trust value for Gene Ontology Extension took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.569697380065918s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.265758752822876s
Reputation | Calculation of the PageRank for Gene Ontology took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0009734630584716797s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0009512901306152344s
Believability | Calculation of trust value for Gene Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.628573417663574s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 8.726119995117188e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.25896286964416504s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0008373260498046875s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.361701965332031e-05s
Believability | Calculation of trust value for Cereal Plant Development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gro took 2.5177485942840576s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 5.817413330078125e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2647700309753418s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.021351337432861328s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00043201446533203125s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.6991944313049316s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2574045658111572s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020290136337280273s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007550716400146484s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.531846761703491s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2528557777404785s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005762577056884766s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hao took 2.6000325679779053s
Availability | SPARQL endpoint availability check for HCPCS took 4.291534423828125e-05s
Availability | VoID file availability check for HCPCS took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2590596675872803s
Reputation | Calculation of the PageRank for HCPCS took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00022792816162109375s
Believability | Calculation of trust value for HCPCS took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.647137403488159s
Availability | SPARQL endpoint availability check for Health Level Seven took 9.965896606445312e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.27487730979919434s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012819766998291016s
Believability | Calculation of trust value for Health Level Seven took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hl7 took 2.5961482524871826s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 8.463859558105469e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2630021572113037s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00034618377685546875s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.63900089263916s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2555875778198242s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-hom took 2.615219831466675s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.315376281738281e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.28224849700927734s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.1948089599609375e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.5837628841400146s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.26659250259399414s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006773471832275391s
Believability | Calculation of trust value for Human Phenotype Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.542360544204712s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.2611050605773926s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020402908325195312s
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.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010519027709960938s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hpio took 2.6248762607574463s
Availability | SPARQL endpoint availability check for HUGO took 5.14984130859375e-05s
Availability | VoID file availability check for HUGO took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for HUGO took 0.26339030265808105s
Reputation | Calculation of the PageRank for HUGO took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for HUGO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.987022399902344e-05s
Believability | Calculation of trust value for HUGO took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hugo took 2.6003522872924805s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.28598809242248535s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0008387565612792969s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0007135868072509766s
Believability | Calculation of trust value for Information Artifact Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-iao took 2.5312113761901855s
Availability | SPARQL endpoint availability check for ICD10 took 4.935264587402344e-05s
Availability | VoID file availability check for ICD10 took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for ICD10 took 0.2684612274169922s
Reputation | Calculation of the PageRank for ICD10 took 0.02089381217956543s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0009007453918457031s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0009169578552246094s
Believability | Calculation of trust value for ICD10 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd10 took 2.849363088607788s
Availability | SPARQL endpoint availability check for ICD10CM took 4.291534423828125e-05s
Availability | VoID file availability check for ICD10CM took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.24838471412658691s
Reputation | Calculation of the PageRank for ICD10CM took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006318092346191406s
Believability | Calculation of trust value for ICD10CM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.5411269664764404s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.267692565917969e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.26441431045532227s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.0001628398895263672s
Believability | Calculation of trust value for ICD-10-PCS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.613370418548584s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.315376281738281e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.24491000175476074s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006527900695800781s
Believability | Calculation of trust value for International Classification of Diseases took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.6398141384124756s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 5.7220458984375e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2509489059448242s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004622936248779297s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.5543668270111084s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.291534423828125e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.27796411514282227s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012841224670410156s
Believability | Calculation of trust value for International Classification for Nursing Practice took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icnp took 2.6261911392211914s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.363059997558594e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2742185592651367s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004918575286865234s
Believability | Calculation of trust value for International Classification of Primary Care took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icpc took 2.50083327293396s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.410743713378906e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.24477624893188477s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008919239044189453s
Believability | Calculation of trust value for ICPC-2 PLUS took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.5964574813842773s
Availability | SPARQL endpoint availability check for ICPS Network took 4.363059997558594e-05s
Availability | VoID file availability check for ICPS Network took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2621779441833496s
Reputation | Calculation of the PageRank for ICPS Network took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00025343894958496094s
Believability | Calculation of trust value for ICPS Network took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-icps took 2.563603162765503s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.24308276176452637s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020847320556640625s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008711814880371094s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ido took 2.4178268909454346s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 5.1021575927734375e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2532942295074463s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011603832244873047s
Believability | Calculation of trust value for Brucellosis Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-idobru took 2.525707244873047s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2717461585998535s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0008816719055175781s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0014100074768066406s
Believability | Calculation of trust value for Malaria Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-idomal took 2.726555347442627s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.5299530029296875e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2475593090057373s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003197193145751953s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-iev took 2.525568962097168s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.267692565917969e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.26857805252075195s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.0001633167266845703s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-imgt took 2.6377995014190674s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.267692565917969e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2637019157409668s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020873546600341797s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0008451938629150391s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005769729614257812s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-imr took 2.511115074157715s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2440481185913086s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007755756378173828s
Believability | Calculation of trust value for Interaction Network Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ino took 2.507641315460205s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.267692565917969e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2590022087097168s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.075599670410156e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.6403329372406006s
Availability | SPARQL endpoint availability check for IxnO took 4.1961669921875e-05s
Availability | VoID file availability check for IxnO took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for IxnO took 0.27420592308044434s
Reputation | Calculation of the PageRank for IxnO took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00019812583923339844s
Believability | Calculation of trust value for IxnO took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ixno took 2.5482163429260254s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.172325134277344e-05s
Availability | VoID file availability check for SysMO-JERM took 0.000579833984375s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2815418243408203s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003800392150878906s
Believability | Calculation of trust value for SysMO-JERM took 3.170967102050781e-05s
INFO | --- Analysis for bioportal-jerm took 2.632270336151123s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.24776124954223633s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.028680086135864258s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0014073848724365234s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 4.9114227294921875e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-kisao took 2.5061254501342773s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.172325134277344e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.267627477645874s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0002067089080810547s
Believability | Calculation of trust value for Loggerhead nesting took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-lhn took 2.5732600688934326s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.28135108947753906s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020503997802734375s
Believability | Calculation of trust value for Lipid Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lipro took 2.6411004066467285s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.315376281738281e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.31246256828308105s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018393993377685547s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lnc took 3.1008377075195312s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.6253204345703125e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.275010347366333s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020754337310791016s
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.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006763935089111328s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ma took 2.688908100128174s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.291534423828125e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2809572219848633s
Reputation | Calculation of the PageRank for Multiple alignment took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00021719932556152344s
Believability | Calculation of trust value for Multiple alignment took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mao took 2.579456090927124s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.291534423828125e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2693920135498047s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007328987121582031s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mat took 2.5498945713043213s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.315376281738281e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.26403212547302246s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020600318908691406s
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.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00045108795166015625s
Believability | Calculation of trust value for Breast tissue cell lines took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.509730577468872s
Availability | SPARQL endpoint availability check for Cell line ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for Cell line ontology took 0.0009365081787109375s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.27501821517944336s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.00077056884765625s
Believability | Calculation of trust value for Cell line ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mccl took 2.6157405376434326s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26053452491760254s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014743804931640625s
Believability | Calculation of trust value for Cell line ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.5564491748809814s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 5.030632019042969e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0009129047393798828s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.2668724060058594s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002465248107910156s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mcv took 2.6185765266418457s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.649162292480469e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2531306743621826s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.021183490753173828s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.001039743423461914s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00025081634521484375s
Believability | Calculation of trust value for Master Drug Data Base took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mddb took 2.576815605163574s
Availability | SPARQL endpoint availability check for MedDRA took 9.036064147949219e-05s
Availability | VoID file availability check for MedDRA took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for MedDRA took 0.24406981468200684s
Reputation | Calculation of the PageRank for MedDRA took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.001172780990600586s
Believability | Calculation of trust value for MedDRA took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mdr took 2.4809861183166504s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.267692565917969e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2353343963623047s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009033679962158203s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.5350427627563477s
Availability | SPARQL endpoint availability check for MeGO took 4.839897155761719e-05s
Availability | VoID file availability check for MeGO took 0.00041174888610839844s
Completeness | Calculation of interlinking completeness for MeGO took 0.25194883346557617s
Reputation | Calculation of the PageRank for MeGO took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for MeGO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014662742614746094s
Believability | Calculation of trust value for MeGO took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mego took 2.5333595275878906s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.3392181396484375e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.29566192626953125s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018472671508789062s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 2.912379503250122s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2650325298309326s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020855426788330078s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006506443023681641s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mf took 2.493232011795044s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.8160552978515625e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2700059413909912s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005571842193603516s
Believability | Calculation of trust value for Medaka fish anatomy and development took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-mfo took 2.5827009677886963s
Availability | SPARQL endpoint availability check for Emotion Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.26638031005859375s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007658004760742188s
Believability | Calculation of trust value for Emotion Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mfoem took 2.541426420211792s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.25606751441955566s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010514259338378906s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mhc took 2.5245494842529297s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.2438507080078125e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.28409242630004883s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.021970033645629883s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0009665489196777344s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0008008480072021484s
Believability | Calculation of trust value for Protein-protein interaction took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mi took 2.6082887649536133s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 6.747245788574219e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2562904357910156s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007414817810058594s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-miro took 2.6025049686431885s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.25935816764831543s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001437664031982422s
Believability | Calculation of trust value for Measurement Method Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mmo took 2.577270030975342s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.24233317375183105s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00038552284240722656s
Believability | Calculation of trust value for MGED Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mo took 2.5954408645629883s
Availability | SPARQL endpoint availability check for Protein modification took 4.1961669921875e-05s
Availability | VoID file availability check for Protein modification took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2526376247406006s
Reputation | Calculation of the PageRank for Protein modification took 0.021105051040649414s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0010223388671875s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002770423889160156s
Believability | Calculation of trust value for Protein modification took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mod took 2.5859758853912354s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.5299530029296875e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2392587661743164s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.0209043025970459s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0007181167602539062s
Believability | Calculation of trust value for Mammalian phenotype took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mp took 2.5817759037017822s
Availability | SPARQL endpoint availability check for Mouse pathology took 5.1021575927734375e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2728087902069092s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020804166793823242s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0005023479461669922s
Believability | Calculation of trust value for Mouse pathology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mpath took 2.5814266204833984s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.38690185546875e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2937023639678955s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003726482391357422s
Believability | Calculation of trust value for Mass spectrometry took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ms took 2.599640130996704s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 8.153915405273438e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3426196575164795s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018703937530517578s
Believability | Calculation of trust value for Medical Subject Headings took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-msh took 3.1256909370422363s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.315376281738281e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2588028907775879s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0010111331939697266s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00022220611572265625s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mthch took 2.616103172302246s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.2546076774597168s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.02108001708984375s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008633136749267578s
Believability | Calculation of trust value for Natural Products Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-natpro took 2.6044933795928955s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 5.14984130859375e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2605893611907959s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02106308937072754s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008723735809326172s
Believability | Calculation of trust value for NCBI organismal classification took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.6759607791900635s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 7.963180541992188e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.33115339279174805s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020198822021484375s
Believability | Calculation of trust value for NCI Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ncit took 3.0219664573669434s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.291534423828125e-05s
Availability | VoID file availability check for National Drug Data File took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.26555299758911133s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006666183471679688s
Believability | Calculation of trust value for National Drug Data File took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-nddf took 2.5878357887268066s
Availability | SPARQL endpoint availability check for National Drug File took 4.2438507080078125e-05s
Availability | VoID file availability check for National Drug File took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2606008052825928s
Reputation | Calculation of the PageRank for National Drug File took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.001306772232055664s
Believability | Calculation of trust value for National Drug File took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.62162446975708s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 5.650520324707031e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2668595314025879s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.021010398864746094s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0012753009796142578s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.593015193939209s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2703840732574463s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0007147789001464844s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-neomark took 2.6529629230499268s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.27080583572387695s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00013637542724609375s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-neomarkontology took 2.64125394821167s
Availability | SPARQL endpoint availability check for NIFSTD took 0.0006287097930908203s
Availability | VoID file availability check for NIFSTD took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.29152679443359375s
Reputation | Calculation of the PageRank for NIFSTD took 0.02442145347595215s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.52587890625e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0013339519500732422s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0022592544555664062s
Believability | Calculation of trust value for NIFSTD took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-nif took 3.011868715286255s
Availability | SPARQL endpoint availability check for NIF Cell took 4.267692565917969e-05s
Availability | VoID file availability check for NIF Cell took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.25923609733581543s
Reputation | Calculation of the PageRank for NIF Cell took 0.02099895477294922s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0014491081237792969s
Believability | Calculation of trust value for NIF Cell took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.634294271469116s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 5.841255187988281e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.27845168113708496s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.001438140869140625s
Believability | Calculation of trust value for NIF Dysfunction took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.639066696166992s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.26018238067626953s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.021124839782714844s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.00060272216796875s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nigo took 2.626234769821167s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.935264587402344e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2400975227355957s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020900487899780273s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0006046295166015625s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nmr took 2.551100015640259s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2559938430786133s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00013971328735351562s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.5312728881835938s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.26241302490234375s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0012102127075195312s
Believability | Calculation of trust value for NanoParticle Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-npo took 2.544739246368408s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.27254199981689453s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007581710815429688s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oae took 2.543837785720825s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.26594996452331543s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0015189647674560547s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-obi took 2.5043551921844482s
Availability | SPARQL endpoint availability check for OBOE took 4.076957702636719e-05s
Availability | VoID file availability check for OBOE took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for OBOE took 0.24441003799438477s
Reputation | Calculation of the PageRank for OBOE took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for OBOE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011754035949707031s
Believability | Calculation of trust value for OBOE took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-oboe took 2.542527914047241s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.220008850097656e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2366936206817627s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008211135864257812s
Believability | Calculation of trust value for OBOE SBC took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.51724910736084s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2767770290374756s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0006532669067382812s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ocre took 2.6648099422454834s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 8.034706115722656e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.00048828125s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.28113603591918945s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008983612060546875s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-odgi took 2.587733507156372s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 5.412101745605469e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2803356647491455s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0009469985961914062s
Believability | Calculation of trust value for Ontology for Genetic Interval took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ogi took 2.611147165298462s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.27661824226379395s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00030303001403808594s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ogmd took 2.620769500732422s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.27631640434265137s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006902217864990234s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ogms took 2.6069564819335938s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.1484832763671875e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.26671385765075684s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.00115966796875s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-omim took 2.5107717514038086s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.2633678913116455s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00037288665771484375s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-omit took 2.569875478744507s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.25580668449401855s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02062702178955078s
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.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006196498870849609s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-omrse took 2.2997257709503174s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 7.390975952148438e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.28235769271850586s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0008161067962646484s
Believability | Calculation of trust value for Ontology of Data Mining took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontodm took 2.728611469268799s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2523341178894043s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00025200843811035156s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ontodt took 2.551307439804077s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.100799560546875e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2532539367675781s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006120204925537109s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.606504440307617s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.696846008300781e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.25536537170410156s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009429454803466797s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-opl took 2.5671534538269043s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.124641418457031e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.25397324562072754s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020390987396240234s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008704662322998047s
Believability | Calculation of trust value for Phenotypic quality took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-pato took 2.651808500289917s
Availability | SPARQL endpoint availability check for Physician Data Query took 6.031990051269531e-05s
Availability | VoID file availability check for Physician Data Query took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2576770782470703s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008625984191894531s
Believability | Calculation of trust value for Physician Data Query took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pdq took 2.5301432609558105s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.3392181396484375e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.25124430656433105s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008616447448730469s
Believability | Calculation of trust value for Pediatric Terminology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pedterm took 2.5714282989501953s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 5.078315734863281e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.25364136695861816s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019860267639160156s
Believability | Calculation of trust value for Parasite Experiment Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-peo took 2.6679272651672363s
Availability | SPARQL endpoint availability check for PHARE took 4.220008850097656e-05s
Availability | VoID file availability check for PHARE took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for PHARE took 0.25191807746887207s
Reputation | Calculation of the PageRank for PHARE took 0.020745277404785156s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006525516510009766s
Believability | Calculation of trust value for PHARE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-phare took 2.6257734298706055s
Availability | SPARQL endpoint availability check for PKO_Re took 5.14984130859375e-05s
Availability | VoID file availability check for PKO_Re took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2680044174194336s
Reputation | Calculation of the PageRank for PKO_Re took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00018715858459472656s
Believability | Calculation of trust value for PKO_Re took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pko took 2.5837769508361816s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.076957702636719e-05s
Availability | VoID file availability check for PMA 2010 took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.24422502517700195s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009675025939941406s
Believability | Calculation of trust value for PMA 2010 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pma took 2.582138776779175s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 6.747245788574219e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2826533317565918s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.021266460418701172s
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.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00018024444580078125s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-pmr took 2.588395357131958s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.792213439941406e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.27692317962646484s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.000392913818359375s
Believability | Calculation of trust value for Plant Anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-po took 2.608640432357788s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 5.2928924560546875e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2685115337371826s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.367134094238281e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.652053117752075s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Plant Ontology took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.273240327835083s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004444122314453125s
Believability | Calculation of trust value for Plant Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.6305809020996094s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.601478576660156e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2710392475128174s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006816387176513672s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pr took 2.588078022003174s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.2438507080078125e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2836775779724121s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020809650421142578s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00027680397033691406s
Believability | Calculation of trust value for Proteomics data and process provenance took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-propreo took 2.687326669692993s
Availability | SPARQL endpoint availability check for Pathway ontology took 7.987022399902344e-05s
Availability | VoID file availability check for Pathway ontology took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.25437116622924805s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012922286987304688s
Believability | Calculation of trust value for Pathway ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pw took 2.5906543731689453s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2534620761871338s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.021027803421020508s
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.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.457069396972656e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-qibo took 2.5999600887298584s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 9.369850158691406e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3271801471710205s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02085113525390625s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017971992492675781s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rcd took 3.148167610168457s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2643001079559326s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00013685226440429688s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rctontology took 2.598594903945923s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.23799967765808105s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02042245864868164s
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.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.584426879882812e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 3.0040740966796875e-05s
INFO | --- Analysis for bioportal-repo took 2.5600972175598145s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.1484832763671875e-05s
Availability | VoID file availability check for Physico-chemical process took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.25261402130126953s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00021195411682128906s
Believability | Calculation of trust value for Physico-chemical process took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rex took 2.561516046524048s
Availability | SPARQL endpoint availability check for RadLex took 4.363059997558594e-05s
Availability | VoID file availability check for RadLex took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for RadLex took 0.2663536071777344s
Reputation | Calculation of the PageRank for RadLex took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for RadLex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015363693237304688s
Believability | Calculation of trust value for RadLex took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rid took 2.6070077419281006s
Availability | SPARQL endpoint availability check for RNA ontology took 4.363059997558594e-05s
Availability | VoID file availability check for RNA ontology took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.27176547050476074s
Reputation | Calculation of the PageRank for RNA ontology took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005803108215332031s
Believability | Calculation of trust value for RNA ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rnao took 2.6813204288482666s
Availability | SPARQL endpoint availability check for Role Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Role Ontology took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2680974006652832s
Reputation | Calculation of the PageRank for Role Ontology took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019431114196777344s
Believability | Calculation of trust value for Role Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-roleo took 2.5278501510620117s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.27698707580566406s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001823902130126953s
Believability | Calculation of trust value for Rat Strain Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rs took 2.5891008377075195s
Availability | SPARQL endpoint availability check for RxNORM took 4.2438507080078125e-05s
Availability | VoID file availability check for RxNORM took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for RxNORM took 0.25457215309143066s
Reputation | Calculation of the PageRank for RxNORM took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006175041198730469s
Believability | Calculation of trust value for RxNORM took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.5106940269470215s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.2438507080078125e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.25757360458374023s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010552406311035156s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sao took 2.5454354286193848s
Availability | SPARQL endpoint availability check for Systems Biology took 4.2438507080078125e-05s
Availability | VoID file availability check for Systems Biology took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.26007533073425293s
Reputation | Calculation of the PageRank for Systems Biology took 0.020503759384155273s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004601478576660156s
Believability | Calculation of trust value for Systems Biology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sbo took 2.5377306938171387s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2733645439147949s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010609626770019531s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sbro took 2.5939600467681885s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.2745647430419922s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0014002323150634766s
Believability | Calculation of trust value for Sleep Domain Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-sdo took 2.534902572631836s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 6.771087646484375e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2662353515625s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.0207674503326416s
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.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003476142883300781s
Believability | Calculation of trust value for Sample processing and separation techniques took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sep took 2.6614463329315186s
Availability | SPARQL endpoint availability check for Student Health Record took 5.435943603515625e-05s
Availability | VoID file availability check for Student Health Record took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.27701377868652344s
Reputation | Calculation of the PageRank for Student Health Record took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004432201385498047s
Believability | Calculation of trust value for Student Health Record took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-shr took 2.63100528717041s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 5.5789947509765625e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2470686435699463s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.021038293838500977s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.001094818115234375s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0013706684112548828s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-sio took 3.2568814754486084s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.1961669921875e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2655763626098633s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020867347717285156s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0002040863037109375s
Believability | Calculation of trust value for Situation-Based Access Control took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-sitbac took 2.5939838886260986s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.482269287109375e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.28944873809814453s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019490718841552734s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-snomedct took 2.9991703033447266s
Availability | SPARQL endpoint availability check for SNP-Ontology took 7.581710815429688e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.26920509338378906s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006759166717529297s
Believability | Calculation of trust value for SNP-Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-snpo took 2.5098023414611816s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.315376281738281e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2681903839111328s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005962848663330078s
Believability | Calculation of trust value for Sequence types and features took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.5514955520629883s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.3392181396484375e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.3273329734802246s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.022048234939575195s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.001619577407836914s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sopharm took 3.0395407676696777s
Availability | SPARQL endpoint availability check for SoyOntology took 4.9591064453125e-05s
Availability | VoID file availability check for SoyOntology took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.26639890670776367s
Reputation | Calculation of the PageRank for SoyOntology took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00013303756713867188s
Believability | Calculation of trust value for SoyOntology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-soy took 2.5480844974517822s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Spider Ontology took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.27900028228759766s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003311634063720703s
Believability | Calculation of trust value for Spider Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-spd took 2.5996336936950684s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2684786319732666s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.021246910095214844s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0003070831298828125s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-spto took 2.629899740219116s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.25794100761413574s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00045228004455566406s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sso took 2.5892999172210693s
Availability | SPARQL endpoint availability check for Software Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Software Ontology took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.25257396697998047s
Reputation | Calculation of the PageRank for Software Ontology took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004296302795410156s
Believability | Calculation of trust value for Software Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-swo took 2.6472699642181396s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.27137112617492676s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00025343894958496094s
Believability | Calculation of trust value for Tick gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tads took 2.597707509994507s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2970705032348633s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0009250640869140625s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tao took 2.605508804321289s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.3392181396484375e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2727820873260498s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.465217590332031e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-taxrank took 2.682462453842163s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.839897155761719e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.24027061462402344s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 9.250640869140625e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-teddy took 2.701800584793091s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2563292980194092s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008451938629150391s
Believability | Calculation of trust value for Time Event Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-teo took 2.5644001960754395s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2519855499267578s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00039196014404296875s
Believability | Calculation of trust value for Mosquito gross anatomy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-tgma took 2.6752333641052246s
Availability | SPARQL endpoint availability check for thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for thesaurus took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2737870216369629s
Reputation | Calculation of the PageRank for thesaurus took 0.02046799659729004s
Interlinking | Calculation of Degree of Connection for thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.67572021484375e-05s
Believability | Calculation of trust value for thesaurus took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.611778497695923s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.935264587402344e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.25407910346984863s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003669261932373047s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.567431688308716s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.24370980262756348s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0009219646453857422s
Believability | Calculation of trust value for Translational Medicine Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tmo took 2.544541597366333s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2674543857574463s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020644426345825195s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00016164779663085938s
Believability | Calculation of trust value for Plant Trait Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-to took 2.565032958984375s
Availability | SPARQL endpoint availability check for TOK_Ontology took 5.2928924560546875e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.27770495414733887s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00020265579223632812s
Believability | Calculation of trust value for TOK_Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tok took 2.558260679244995s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.744529724121094e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2687044143676758s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019550323486328125s
Believability | Calculation of trust value for Teleost taxonomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tto took 2.5786335468292236s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2569601535797119s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010933876037597656s
Believability | Calculation of trust value for Uber anatomy ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-uberon took 2.6044559478759766s
Availability | SPARQL endpoint availability check for Units Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Units Ontology took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.24623346328735352s
Reputation | Calculation of the PageRank for Units Ontology took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00024056434631347656s
Believability | Calculation of trust value for Units Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.6531596183776855s
Availability | SPARQL endpoint availability check for Units of measurement took 4.220008850097656e-05s
Availability | VoID file availability check for Units of measurement took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2588531970977783s
Reputation | Calculation of the PageRank for Units of measurement took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0008971691131591797s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0003368854522705078s
Believability | Calculation of trust value for Units of measurement took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-uo took 2.517543315887451s
Availability | SPARQL endpoint availability check for VANDF took 4.3392181396484375e-05s
Availability | VoID file availability check for VANDF took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for VANDF took 0.2832610607147217s
Reputation | Calculation of the PageRank for VANDF took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for VANDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007135868072509766s
Believability | Calculation of trust value for VANDF took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vandf took 2.526437759399414s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.24991178512573242s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004277229309082031s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vao took 2.4915289878845215s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.506111145019531e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.29340648651123047s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0008311271667480469s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006592273712158203s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-vhog took 2.619816541671753s
Availability | SPARQL endpoint availability check for VIVO took 4.2438507080078125e-05s
Availability | VoID file availability check for VIVO took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for VIVO took 0.25526857376098633s
Reputation | Calculation of the PageRank for VIVO took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for VIVO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003628730773925781s
Believability | Calculation of trust value for VIVO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vivo took 2.5644068717956543s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.2568228244781494s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012674331665039062s
Believability | Calculation of trust value for Vaccine Ontology took 3.0994415283203125e-05s
INFO | --- Analysis for bioportal-vo took 2.5170793533325195s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.24262619018554688s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020694732666015625s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 1.9550323486328125e-05s
INFO | --- Analysis for bioportal-vt took 2.4861366748809814s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.26038122177124023s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005614757537841797s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-wbbt took 2.5295960903167725s
Availability | SPARQL endpoint availability check for C. elegans development took 4.220008850097656e-05s
Availability | VoID file availability check for C. elegans development took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2685081958770752s
Reputation | Calculation of the PageRank for C. elegans development took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.9114227294921875e-05s
Believability | Calculation of trust value for C. elegans development took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-wbls took 2.6054325103759766s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.315376281738281e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.26669764518737793s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.96453857421875e-05s
Believability | Calculation of trust value for C. elegans phenotype took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.5295419692993164s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.267692565917969e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.24800491333007812s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006415843963623047s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-who took 2.56087589263916s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.4345855712890625e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2691788673400879s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006997585296630859s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-xao took 2.579190254211426s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 5.173683166503906e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.23967528343200684s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002384185791015625s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-xco took 2.5919249057769775s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.267692565917969e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.256777286529541s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00026607513427734375s
Believability | Calculation of trust value for Yeast phenotypes took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ypo took 2.561383008956909s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.220008850097656e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2678396701812744s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007741451263427734s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-zfa took 2.6122777462005615s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 6.4849853515625e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.25788187980651855s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 7.62939453125e-06s
INFO | --- Analysis for Bioportal_link took 3.888979434967041s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.440110445022583s
Availability | VoID file availability check for BioSamples RDF took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2552042007446289s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.814697265625e-05s
Believability | Calculation of trust value for BioSamples RDF took 8.58306884765625e-06s
INFO | --- Analysis for biosamples-rdf took 3.449526071548462s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.5310847759246826s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2685201168060303s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00012087821960449219s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for bis-linked-data took 2.9429473876953125s
Availability | SPARQL endpoint availability check for Bitzi took 4.3392181396484375e-05s
Availability | VoID file availability check for Bitzi took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Bitzi took 0.25237536430358887s
Reputation | Calculation of the PageRank for Bitzi took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.4332275390625e-05s
Believability | Calculation of trust value for Bitzi took 8.344650268554688e-06s
INFO | --- Analysis for bitzi took 2.8430864810943604s
Availability | SPARQL endpoint availability check for BizkaiSense took 3.933906555175781e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.284820556640625s
Reputation | Calculation of the PageRank for BizkaiSense took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.409385681152344e-05s
Believability | Calculation of trust value for BizkaiSense took 8.344650268554688e-06s
INFO | --- Analysis for bizkaisense took 2.880211353302002s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.029273986816406e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.26818227767944336s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.0204925537109375s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.075599670410156e-05s
Believability | Calculation of trust value for blabla.itemlist took 8.106231689453125e-06s
INFO | --- Analysis for blabla-itemlist took 2.97796630859375s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.076957702636719e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2573676109313965s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020667314529418945s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0994415283203125e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.867813110351562e-06s
INFO | --- Analysis for blabla_itemlist took 2.8970320224761963s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 5.602836608886719e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.24988031387329102s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.124641418457031e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for bll-thesaurus took 3.69146466255188s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.3393423557281494s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.2879002094268799s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.021020174026489258s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0008318424224853516s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 7.62939453125e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for bluk-bnb took 11.594276666641235s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.34087514877319336s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006539821624755859s
Extra | Recovery of all triples for Thesaurus BNCF took 49.921125650405884s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6515712738037109s
Amount of data | Number of triples check for Thesaurus BNCF took 0.7270841598510742s
Interoperability | New terms check for Thesaurus BNCF took 1.4965155124664307s
Versatility | Languages check for Thesaurus BNCF took 7.32319974899292s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.9395067691802979s
Security | Check HTTPS for Thesaurus BNCF took 0.10905027389526367s
Interpretability | RDF structures check for Thesaurus BNCF took 0.12598729133605957s
Versatility | Serialization formats check for Thesaurus BNCF took 0.12292957305908203s
Availability | RDF dump link check for Thesaurus BNCF took 0.10782909393310547s
License | MR license check for Thesaurus BNCF took 0.1128702163696289s
License | HR license check for Thesaurus BNCF took 0.2040703296661377s
Amount of data | Number of property check for Thesaurus BNCF took 0.12016725540161133s
Understandability | Number of label check for Thesaurus BNCF took 0.27223849296569824s
Understandability | URI regex check for Thesaurus BNCF took 0.24209332466125488s
Understandability | Vocabs check for Thesaurus BNCF took 0.12654471397399902s
Verifiability | Authors check for Thesaurus BNCF took 0.12290287017822266s
Verifiability | Publishers check for Thesaurus BNCF took 0.1127324104309082s
Performance | Throughput check for Thesaurus BNCF took 10.711859941482544s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.295608520507812e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.12947368621826172s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12142276763916016s
Interlinking | skos check for Thesaurus BNCF took 0.18437457084655762s
Interlinking | skos check for Thesaurus BNCF took 0.15711307525634766s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.12709283828735352s
Currency | Creation date check for Thesaurus BNCF took 0.2387070655822754s
Currency | Modification date check for Thesaurus BNCF took 0.23908591270446777s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.089778900146484s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.1645030975341797s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.11734414100646973s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11604881286621094s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.43743371963501s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5145986080169678s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.086675643920898s
Consistency | Disjoint class check for Thesaurus BNCF took 0.13886451721191406s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.9899380207061768s
Consistency | Misplaced classes for Thesaurus BNCF took 7.088000059127808s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.189208030700684s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4699838161468506s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.3032355308532715s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4555554389953613s
Security | Sign check for Thesaurus BNCF took 0.11640810966491699s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 22.06292486190796s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2773265838623047s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.891654968261719e-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 7.62939453125e-06s
INFO | --- Analysis for bncf-ns took 195.0461483001709s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4690389633178711s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.000667572021484375s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9237775802612305s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6693360805511475s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.369177341461182s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.3160319328308105s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.343984603881836s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.174251317977905s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3972203731536865s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3963444232940674s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.49163055419921875s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.48918962478637695s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5535016059875488s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.31827640533447s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3233788013458252s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8599905967712402s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6332676410675049s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4603421688079834s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3001265525817871s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3701894283294678s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.793418645858765s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.486343383789062e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35982394218444824s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3965740203857422s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.24593400955200195s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2907993793487549s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.43323588371276855s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7743902206420898s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3443484306335449s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.49482274055481s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3043553829193115s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33092546463012695s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3354361057281494s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8993916511535645s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.023806095123291016s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028714418411254883s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34796762466430664s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.61099100112915s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.40091443061828613s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3593506813049316s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5804660320281982s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.121949911117554s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.031203269958496094s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6540441513061523s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31555676460266113s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.668171405792236s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2116060256958008s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.106231689453125e-06s
INFO | --- Analysis for bpr took 398.8699412345886s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.649162292480469e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.7553467750549316s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.939338684082031e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.0067901611328125e-06s
INFO | --- Analysis for brazilian-politicians took 4.356861352920532s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.100799560546875e-05s
Availability | VoID file availability check for BrazilianCities took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.2757563591003418s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 2.956390380859375e-05s
Believability | Calculation of trust value for BrazilianCities took 7.3909759521484375e-06s
INFO | --- Analysis for braziliancities took 3.834545135498047s
Availability | SPARQL endpoint availability check for Bricklink took 1.79136061668396s
Availability | VoID file availability check for Bricklink took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Bricklink took 0.25972604751586914s
Reputation | Calculation of the PageRank for Bricklink took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.866455078125e-05s
Believability | Calculation of trust value for Bricklink took 7.3909759521484375e-06s
INFO | --- Analysis for bricklink took 10.567567110061646s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.258848667144775s
Availability | VoID file availability check for British Museum Collection took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2619047164916992s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 2.9087066650390625e-05s
Believability | Calculation of trust value for British Museum Collection took 6.9141387939453125e-06s
INFO | --- Analysis for british-museum-collection took 73.60545992851257s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 5.221366882324219e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.6916940212249756s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02258777618408203s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0011165142059326172s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.9114227294921875e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 9.775161743164062e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 4.182865381240845s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.076957702636719e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.25464296340942383s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02031087875366211s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.9325485229492188e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.3909759521484375e-06s
INFO | --- Analysis for bsv took 4.202674388885498s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.2538301944732666s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2783994674682617s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02097463607788086s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.3909759521484375e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 7.290968894958496s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.220008850097656e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.2489175796508789s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.0517578125e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 7.62939453125e-06s
INFO | --- Analysis for bund-offener-haushalt took 3.283290386199951s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.410743713378906e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.25281405448913574s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.021584510803222656s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0008628368377685547s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.552436828613281e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 8.106231689453125e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.9252753257751465s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.2395925521850586s
Availability | VoID file availability check for business.data.gov.uk took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.23059916496276855s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020289182662963867s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 4.1484832763671875e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 4.935264587402344e-05s
Believability | Calculation of trust value for business.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for business-data-gov-uk took 2.7111032009124756s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5986988544464111s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0007326602935791016s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 5.0787270069122314s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.6667349338531494s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.44061994552612305s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7580277919769287s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 30.830145359039307s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.36243724822998047s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.2214796543121338s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5622146129608154s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.355454683303833s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.32523393630981445s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.45296216011047363s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 12.643092632293701s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3495919704437256s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.7940959930419922s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6681373119354248s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3665010929107666s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.3397505283355713s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3733532428741455s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.829841613769531s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.367134094238281e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.33542823791503906s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.35577869415283203s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.45966458320617676s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3235137462615967s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.3471102714538574s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.7359933853149414s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.6795060634613037s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.1030428409576416s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.34293699264526367s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5175120830535889s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5096216201782227s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.025975227355957s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03180527687072754s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.0278475284576416s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.435866117477417s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.530846118927002s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.41115903854370117s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.234119176864624s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2809724807739258s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.46208119392395s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03269553184509277s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.3784036636352539s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3747541904449463s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 10068.053511619568s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.1710546016693115s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02169632911682129s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.001065969467163086s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 2.1457672119140625e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 8.106231689453125e-06s
INFO | --- Analysis for BVMC took 10280.168603897095s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 7.605552673339844e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.7068607807159424s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0008318424224853516s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.3855438232421875e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.62939453125e-06s
INFO | --- Analysis for cabbage took 5.589073657989502s
Availability | SPARQL endpoint availability check for cablegate took 1.742220163345337s
Availability | VoID file availability check for cablegate took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for cablegate took 0.26495909690856934s
Reputation | Calculation of the PageRank for cablegate took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for cablegate took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.43865966796875e-05s
Believability | Calculation of trust value for cablegate took 6.67572021484375e-06s
INFO | --- Analysis for cablegate took 6.8693366050720215s
Availability | SPARQL endpoint availability check for Calames took 4.363059997558594e-05s
Availability | VoID file availability check for Calames took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Calames took 0.27977991104125977s
Reputation | Calculation of the PageRank for Calames took 0.021053552627563477s
Interlinking | Calculation of Degree of Connection for Calames took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Calames took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for Calames took 3.8623809814453125e-05s
Believability | Calculation of trust value for Calames took 6.9141387939453125e-06s
INFO | --- Analysis for calames took 6.47871208190918s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.44315600395202637s
Availability | VoID file availability check for CaLiGraph took 0.00025200843811035156s
Extra | Recovery of all triples for CaLiGraph took 1.9185905456542969s
Performance | Total latancy measurement for CaLiGraph took 1.1739437580108643s
Amount of data | Number of triples check for CaLiGraph took 12.62771487236023s
Interoperability | New terms check for CaLiGraph took 2.018279790878296s
Versatility | Languages check for CaLiGraph took 60.32487988471985s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2457125186920166s
Security | Check HTTPS for CaLiGraph took 0.13925814628601074s
Interpretability | RDF structures check for CaLiGraph took 0.2790048122406006s
Versatility | Serialization formats check for CaLiGraph took 0.3263092041015625s
Availability | RDF dump link check for CaLiGraph took 0.2575373649597168s
License | MR license check for CaLiGraph took 0.4222099781036377s
License | HR license check for CaLiGraph took 60.29933142662048s
Amount of data | Number of property check for CaLiGraph took 0.25919246673583984s
Understandability | Number of label check for CaLiGraph took 3.2377235889434814s
Understandability | URI regex check for CaLiGraph took 0.5456595420837402s
Understandability | Vocabs check for CaLiGraph took 0.29038500785827637s
Verifiability | Authors check for CaLiGraph took 0.2777268886566162s
Verifiability | Publishers check for CaLiGraph took 0.2570822238922119s
Performance | Throughput check for CaLiGraph took 11.377208948135376s
Amount of data | Check the number of entities for CaLiGraph took 0.017280101776123047s
Verifiability | Contribs. check for CaLiGraph took 0.2729203701019287s
Interlinking | sameAs chians check for CaLiGraph took 0.7149856090545654s
Interlinking | skos check for CaLiGraph took 0.39886927604675293s
Interlinking | skos check for CaLiGraph took 0.21969223022460938s
Timeliness | dataset update frequency check for CaLiGraph took 0.30452632904052734s
Currency | Creation date check for CaLiGraph took 0.5244505405426025s
Currency | Modification date check for CaLiGraph took 0.5294644832611084s
Rep.Conc. | URIs length for CaLiGraph took 61.13254976272583s
Interoperability | New vocabularies check for CaLiGraph took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2471458911895752s
Accuracy | Check Functional Property for CaLiGraph took 0.32262349128723145s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.29207539558410645s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6445801258087158s
Accuracy | Check White space in annotation for CaLiGraph took 0.026681184768676758s
Accuracy | Check Datatype consistency for CaLiGraph took 0.051991939544677734s
Consistency | Disjoint class check for CaLiGraph took 0.24528884887695312s
Consistency | Check Misplaced properties for CaLiGraph took 60.99550223350525s
Consistency | Misplaced classes for CaLiGraph took 0.5244159698486328s
Consistency | Check Ontology hijacking for CaLiGraph took 2.1039702892303467s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3289062976837158s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.57323956489563s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03306078910827637s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.5118799209594727s
Security | Sign check for CaLiGraph took 0.4173109531402588s
Availability | Check URIs Dereferenciability for CaLiGraph took 11.666280508041382s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.8265171051025391s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 7.3909759521484375e-06s
INFO | --- Analysis for CaLiGraph took 1452.208955526352s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.27517080307006836s
Availability | VoID file availability check for CaLiGraph took 0.0002770423889160156s
Extra | Recovery of all triples for CaLiGraph took 1.7047691345214844s
Performance | Total latancy measurement for CaLiGraph took 1.1388323307037354s
Amount of data | Number of triples check for CaLiGraph took 12.453435897827148s
Interoperability | New terms check for CaLiGraph took 2.1039669513702393s
Versatility | Languages check for CaLiGraph took 60.308273792266846s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2558441162109375s
Security | Check HTTPS for CaLiGraph took 0.15442419052124023s
Interpretability | RDF structures check for CaLiGraph took 0.2666051387786865s
Versatility | Serialization formats check for CaLiGraph took 0.26607775688171387s
Availability | RDF dump link check for CaLiGraph took 0.25267720222473145s
License | MR license check for CaLiGraph took 0.2683396339416504s
License | HR license check for CaLiGraph took 60.346537590026855s
Amount of data | Number of property check for CaLiGraph took 0.25604248046875s
Understandability | Number of label check for CaLiGraph took 3.067742109298706s
Understandability | URI regex check for CaLiGraph took 0.5564672946929932s
Understandability | Vocabs check for CaLiGraph took 0.2749664783477783s
Verifiability | Authors check for CaLiGraph took 0.2648427486419678s
Verifiability | Publishers check for CaLiGraph took 0.24570822715759277s
Performance | Throughput check for CaLiGraph took 11.199687480926514s
Amount of data | Check the number of entities for CaLiGraph took 0.013861894607543945s
Verifiability | Contribs. check for CaLiGraph took 0.24758195877075195s
Interlinking | sameAs chians check for CaLiGraph took 0.6734201908111572s
Interlinking | skos check for CaLiGraph took 0.2512483596801758s
Interlinking | skos check for CaLiGraph took 0.2244710922241211s
Timeliness | dataset update frequency check for CaLiGraph took 0.24762701988220215s
Currency | Creation date check for CaLiGraph took 0.5148019790649414s
Currency | Modification date check for CaLiGraph took 0.5172183513641357s
Rep.Conc. | URIs length for CaLiGraph took 61.63488793373108s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.26532864570617676s
Accuracy | Check Functional Property for CaLiGraph took 0.28760576248168945s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.25551819801330566s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5785479545593262s
Accuracy | Check White space in annotation for CaLiGraph took 0.026462554931640625s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05153775215148926s
Consistency | Disjoint class check for CaLiGraph took 0.24579906463623047s
Consistency | Check Misplaced properties for CaLiGraph took 61.00641179084778s
Consistency | Misplaced classes for CaLiGraph took 0.6097354888916016s
Consistency | Check Ontology hijacking for CaLiGraph took 2.089799165725708s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3137147426605225s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.61098003387451s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029938936233520508s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.448606014251709s
Security | Sign check for CaLiGraph took 0.2591698169708252s
Availability | Check URIs Dereferenciability for CaLiGraph took 12.011436462402344s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.4323861598968506s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 8.344650268554688e-06s
INFO | --- Analysis for caligraph took 1460.3414487838745s
Availability | SPARQL endpoint availability check for can-link took 4.172325134277344e-05s
Availability | VoID file availability check for can-link took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for can-link took 0.2659940719604492s
Reputation | Calculation of the PageRank for can-link took 0.021286487579345703s
Interlinking | Calculation of Degree of Connection for can-link took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for can-link took 0.0010237693786621094s
Interlinking | Calculation of Clustering coefficient for can-link took 4.267692565917969e-05s
Believability | Calculation of trust value for can-link took 8.58306884765625e-06s
INFO | --- Analysis for can-link took 5.515515089035034s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07427716255187988s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2774498462677002s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 6.67572021484375e-06s
INFO | --- Analysis for cap-italy-rdf took 3.4364967346191406s
Availability | SPARQL endpoint availability check for person took 9.107589721679688e-05s
Availability | VoID file availability check for person took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for person took 0.2729182243347168s
Reputation | Calculation of the PageRank for person took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for person took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for person took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for person took 3.457069396972656e-05s
Believability | Calculation of trust value for person took 7.867813110351562e-06s
INFO | --- Analysis for card took 3.2710893154144287s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.291534423828125e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2648923397064209s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 6.9141387939453125e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.5618927478790283s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.0531158447265625e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.2576167583465576s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.0517578125e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.867813110351562e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.850350856781006s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.6086888313293457s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0002589225769042969s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 126.81022524833679s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 1.0053224563598633s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 8.289246082305908s
Interoperability | New terms check for Norway catch records dataset @PSNC took 15.149243354797363s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.2299134731293s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 3.2118425369262695s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.2577822208404541s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 11.07047438621521s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.2879774570465088s
License | MR license check for Norway catch records dataset @PSNC took 0.5624861717224121s
License | HR license check for Norway catch records dataset @PSNC took 300.17764115333557s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.3101828098297119s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.51343035697937s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.91452956199646s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.501291036605835s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.22022151947021484s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.27469778060913086s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.532753705978394s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.82012939453125e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.1860489845275879s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.20882606506347656s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4555208683013916s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.5346336364746094s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 7.09101676940918s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.5016071796417236s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.20492768287658691s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 157.54646635055542s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.18097758293151855s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.2931656837463379s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.29981017112731934s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 42.47465205192566s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.680845260620117s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.640406847000122s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.20908713340759277s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 82.75620818138123s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.42032527923584s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 37.45435357093811s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.3828749656677246s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 86.31874823570251s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.7414069175720215s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5795779228210449s
Security | Sign check for Norway catch records dataset @PSNC took 0.6955885887145996s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 10.48872423171997s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 1.1899549961090088s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.021225929260253906s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2288.5407388210297s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.673004150390625e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.6847889423370361s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.021136760711669922s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00011348724365234375s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.5974044799804688e-05s
INFO | --- Analysis for ce4r took 43.4996178150177s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.46326112747192383s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002875328063964844s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.4112067222595215s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7427022457122803s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.42809081077575684s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6716887950897217s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.115381956100464s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17109370231628418s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3117396831512451s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17731714248657227s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1404252052307129s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26935291290283203s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.36930227279663086s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1468806266784668s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3315870761871338s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28218746185302734s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1573929786682129s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2261064052581787s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1933896541595459s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.689615964889526s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 0.00012636184692382812s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22159075736999512s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14779067039489746s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.46637606620788574s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.12475848197937012s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15540528297424316s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6377236843109131s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3966817855834961s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.2425389289855957s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1373920440673828s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.24441003799438477s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2395944595336914s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6601154804229736s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028439998626708984s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028786659240722656s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3139176368713379s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.193216323852539s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.1137053966522217s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3408024311065674s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5315089225769043s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03254508972167969s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.19733405113220215s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17415356636047363s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2137.0894837379456s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.40061616897583s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.021467208862304688s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 5.125999450683594e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 8.106231689453125e-06s
INFO | --- Analysis for ceo took 2281.318667650223s
Availability | SPARQL endpoint availability check for Charging Stations took 4.220008850097656e-05s
Availability | VoID file availability check for Charging Stations took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.28055906295776367s
Reputation | Calculation of the PageRank for Charging Stations took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.123283386230469e-05s
Believability | Calculation of trust value for Charging Stations took 7.152557373046875e-06s
INFO | --- Analysis for charging-stations took 5.639370918273926s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.506111145019531e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.27378177642822266s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 4.029273986816406e-05s
Believability | Calculation of trust value for Chat Game corpus took 8.106231689453125e-06s
INFO | --- Analysis for chat-game-corpus took 12.574578762054443s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 5.817413330078125e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.2845911979675293s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 8.106231689453125e-06s
INFO | --- Analysis for chebi took 2.8640050888061523s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.38690185546875e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0007405281066894531s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.28328466415405273s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02100396156311035s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.698204040527344e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.152557373046875e-06s
INFO | --- Analysis for chem2bio2rdf took 134.65737056732178s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5641918182373047s
Availability | VoID file availability check for ChEMBL RDF took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.24196529388427734s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.982948303222656e-05s
Believability | Calculation of trust value for ChEMBL RDF took 7.62939453125e-06s
INFO | --- Analysis for chembl-rdf took 4.439255714416504s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.034710168838501s
Availability | VoID file availability check for chemdb  dataset took 0.0002617835998535156s
Extra | Recovery of all triples for chemdb  dataset took 10.419288873672485s
Performance | Total latancy measurement for chemdb  dataset took 2.505398988723755s
Amount of data | Number of triples check for chemdb  dataset took 0.5463476181030273s
Interoperability | New terms check for chemdb  dataset took 3.940931558609009s
Versatility | Languages check for chemdb  dataset took 27.103740692138672s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5170230865478516s
Interpretability | RDF structures check for chemdb  dataset took 0.7266321182250977s
Versatility | Serialization formats check for chemdb  dataset took 1.3457586765289307s
Availability | RDF dump link check for chemdb  dataset took 0.48843836784362793s
License | MR license check for chemdb  dataset took 2.351086378097534s
License | HR license check for chemdb  dataset took 3.7036404609680176s
Amount of data | Number of property check for chemdb  dataset took 0.5211749076843262s
Understandability | Number of label check for chemdb  dataset took 2.246047019958496s
Understandability | URI regex check for chemdb  dataset took 1.9087333679199219s
Understandability | Vocabs check for chemdb  dataset took 0.7947373390197754s
Verifiability | Authors check for chemdb  dataset took 0.7932217121124268s
Verifiability | Publishers check for chemdb  dataset took 0.8103961944580078s
Performance | Throughput check for chemdb  dataset took 13.472564458847046s
Amount of data | Check the number of entities for chemdb  dataset took 6.747245788574219e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.8235981464385986s
Interlinking | sameAs chians check for chemdb  dataset took 0.8298075199127197s
Interlinking | skos check for chemdb  dataset took 2.0135881900787354s
Interlinking | skos check for chemdb  dataset took 0.4951503276824951s
Timeliness | dataset update frequency check for chemdb  dataset took 1.105292558670044s
Currency | Creation date check for chemdb  dataset took 1.3362345695495605s
Currency | Modification date check for chemdb  dataset took 1.0411884784698486s
Rep.Conc. | URIs length for chemdb  dataset took 3.4155471324920654s
Interoperability | New vocabularies check for chemdb  dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5285732746124268s
Accuracy | Check Functional Property for chemdb  dataset took 0.7982094287872314s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.7544326782226562s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.9044618606567383s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030398130416870117s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.033972740173339844s
Consistency | Disjoint class check for chemdb  dataset took 0.821479320526123s
Consistency | Check Misplaced properties for chemdb  dataset took 1.22255277633667s
Consistency | Misplaced classes for chemdb  dataset took 0.6110401153564453s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.958469867706299s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3122355937957764s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.0256714820861816s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.032114267349243164s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5181562900543213s
Security | Sign check for chemdb  dataset took 1.9488253593444824s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2661.002472639084s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 1.128481149673462s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.025057315826416016s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0010228157043457031s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 2.384185791015625e-06s
Believability | Calculation of trust value for chemdb  dataset took 7.62939453125e-06s
INFO | --- Analysis for chemdb-basicInfo took 3744.577268600464s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5264286994934082s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00025963783264160156s
Extra | Recovery of all triples for chemdb estimated properties dataset took 14.837151288986206s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.5092661380767822s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5385494232177734s
Interoperability | New terms check for chemdb estimated properties dataset took 4.251370906829834s
Versatility | Languages check for chemdb estimated properties dataset took 26.17401957511902s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5283870697021484s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5462608337402344s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.3238155841827393s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.761904239654541s
License | MR license check for chemdb estimated properties dataset took 2.600536346435547s
License | HR license check for chemdb estimated properties dataset took 3.9804530143737793s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5177924633026123s
Understandability | Number of label check for chemdb estimated properties dataset took 4.4091103076934814s
Understandability | URI regex check for chemdb estimated properties dataset took 1.6948072910308838s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.7600228786468506s
Verifiability | Authors check for chemdb estimated properties dataset took 0.8741238117218018s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.7735006809234619s
Performance | Throughput check for chemdb estimated properties dataset took 13.632195234298706s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 6.008148193359375e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.7655990123748779s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.0977108478546143s
Interlinking | skos check for chemdb estimated properties dataset took 1.7713346481323242s
Interlinking | skos check for chemdb estimated properties dataset took 0.49491262435913086s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.0493223667144775s
Currency | Creation date check for chemdb estimated properties dataset took 1.2825100421905518s
Currency | Modification date check for chemdb estimated properties dataset took 1.0299839973449707s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.6043176651000977s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.49608707427978516s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7754092216491699s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7455501556396484s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 3.3372743129730225s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.029954910278320312s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03306388854980469s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.8160262107849121s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2121636867523193s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.5983302593231201s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 4.15833854675293s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.300417423248291s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9981944561004639s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03251481056213379s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5245306491851807s
Security | Sign check for chemdb estimated properties dataset took 2.357102155685425s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2674.2209947109222s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 1.5671749114990234s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.021328210830688477s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.2928924560546875e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 9.059906005859375e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 3751.9333333969116s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5278663635253906s
Availability | VoID file availability check for chemdb phase transition dataset took 0.000270843505859375s
Extra | Recovery of all triples for chemdb phase transition dataset took 10.500816345214844s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.4989373683929443s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5506894588470459s
Interoperability | New terms check for chemdb phase transition dataset took 4.2463555335998535s
Versatility | Languages check for chemdb phase transition dataset took 28.577247381210327s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.514970064163208s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5270583629608154s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.4962732791900635s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8536393642425537s
License | MR license check for chemdb phase transition dataset took 3.1320221424102783s
License | HR license check for chemdb phase transition dataset took 4.069650888442993s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5310554504394531s
Understandability | Number of label check for chemdb phase transition dataset took 5.944574356079102s
Understandability | URI regex check for chemdb phase transition dataset took 1.9526121616363525s
Understandability | Vocabs check for chemdb phase transition dataset took 0.8776247501373291s
Verifiability | Authors check for chemdb phase transition dataset took 2.2045767307281494s
Verifiability | Publishers check for chemdb phase transition dataset took 0.8494179248809814s
Performance | Throughput check for chemdb phase transition dataset took 11.98122763633728s
Amount of data | Check the number of entities for chemdb phase transition dataset took 8.225440979003906e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.832667350769043s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.186330795288086s
Interlinking | skos check for chemdb phase transition dataset took 2.0029897689819336s
Interlinking | skos check for chemdb phase transition dataset took 0.4980621337890625s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.1755709648132324s
Currency | Creation date check for chemdb phase transition dataset took 1.3982186317443848s
Currency | Modification date check for chemdb phase transition dataset took 1.0397143363952637s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.607201099395752s
Interoperability | New vocabularies check for chemdb phase transition dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.501150369644165s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.848182201385498s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.7467081546783447s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 3.5553431510925293s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.031012773513793945s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03320765495300293s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.8708806037902832s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.224745750427246s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6146998405456543s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 4.099275588989258s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.27089524269104s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.98624587059021s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.032552480697631836s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5235888957977295s
Security | Sign check for chemdb phase transition dataset took 2.1563079357147217s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2668.3070166110992s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 1.6133954524993896s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021091222763061523s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 7.3909759521484375e-06s
INFO | --- Analysis for chemdb-phaseTransition took 3752.564106464386s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5226180553436279s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00029754638671875s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 10.737881660461426s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.49509596824646s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.562018632888794s
Interoperability | New terms check for chemdb thermochemistry dataset took 4.181021690368652s
Versatility | Languages check for chemdb thermochemistry dataset took 29.37844181060791s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.518435001373291s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5296814441680908s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.570807695388794s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.8624386787414551s
License | MR license check for chemdb thermochemistry dataset took 3.435044288635254s
License | HR license check for chemdb thermochemistry dataset took 4.247354507446289s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5178289413452148s
Understandability | Number of label check for chemdb thermochemistry dataset took 6.269659519195557s
Understandability | URI regex check for chemdb thermochemistry dataset took 2.1644136905670166s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.902679443359375s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.2472481727600098s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.9027261734008789s
Performance | Throughput check for chemdb thermochemistry dataset took 12.947719812393188s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.319450378417969e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.8834073543548584s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.086012601852417s
Interlinking | skos check for chemdb thermochemistry dataset took 2.4774763584136963s
Interlinking | skos check for chemdb thermochemistry dataset took 0.501533031463623s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.2664554119110107s
Currency | Creation date check for chemdb thermochemistry dataset took 1.4289257526397705s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0217406749725342s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.646620750427246s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.4912252426147461s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.8556339740753174s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.8272790908813477s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 3.390941858291626s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.029957294464111328s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03456878662109375s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.6317610740661621s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2260713577270508s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6119821071624756s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 4.238435745239258s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.3332288265228271s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.0319933891296387s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.035953521728515625s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.528369665145874s
Security | Sign check for chemdb thermochemistry dataset took 2.2115821838378906s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2658.969347715378s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 1.6067333221435547s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.021247148513793945s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 8.106231689453125e-06s
INFO | --- Analysis for chemdb-thermochemistry took 3753.618278026581s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 7.033348083496094e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0007674694061279297s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.7002842426300049s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020929336547851562s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.6927719116210938e-05s
INFO | --- Analysis for chempedia-rdf took 11.872119903564453s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.315376281738281e-05s
Availability | VoID file availability check for Chiman Maru took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.6932101249694824s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.0040740966796875e-05s
Believability | Calculation of trust value for Chiman Maru took 7.62939453125e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 3.6537325382232666s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 393.04815196990967s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0003387928009033203s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.6857826709747314s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.020813703536987305s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.790855407714844e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.867813110351562e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 801.1200969219208s
Availability | SPARQL endpoint availability check for Chronicling America took 4.220008850097656e-05s
Availability | VoID file availability check for Chronicling America took 0.0003604888916015625s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.25322675704956055s
Reputation | Calculation of the PageRank for Chronicling America took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010776519775390625s
Believability | Calculation of trust value for Chronicling America took 7.3909759521484375e-06s
INFO | --- Analysis for chronicling-america took 8.462551355361938s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 1028.8902966976166s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.7868001461029053s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.0001380443572998047s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for cht took 1825.1371231079102s
Availability | SPARQL endpoint availability check for ciard-ring took 4.649162292480469e-05s
Availability | VoID file availability check for ciard-ring took 0.0004012584686279297s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2641315460205078s
Reputation | Calculation of the PageRank for ciard-ring took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 5.3882598876953125e-05s
Believability | Calculation of trust value for ciard-ring took 8.106231689453125e-06s
INFO | --- Analysis for ciard-ring took 6.54059910774231s
Availability | SPARQL endpoint availability check for Cine Figure took 4.744529724121094e-05s
Availability | VoID file availability check for Cine Figure took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.6945586204528809s
Reputation | Calculation of the PageRank for Cine Figure took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.458427429199219e-05s
Believability | Calculation of trust value for Cine Figure took 6.4373016357421875e-06s
INFO | --- Analysis for Cine_Figure took 3.6924784183502197s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.18552041053772s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.7189071178436279s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.021032333374023438s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 0.00011587142944335938s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 176.40215373039246s
Availability | SPARQL endpoint availability check for CIPFA took 4.458427429199219e-05s
Availability | VoID file availability check for CIPFA took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2807133197784424s
Reputation | Calculation of the PageRank for CIPFA took 0.020977258682250977s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.886222839355469e-05s
Believability | Calculation of trust value for CIPFA took 5.9604644775390625e-06s
INFO | --- Analysis for cipfa took 4.424743175506592s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.05228114128113s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0007495880126953125s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.35277819633483887s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003981590270996094s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 7.867813110351562e-06s
INFO | --- Analysis for ckan took 263.56350779533386s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.529055118560791s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.27834391593933105s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.02185988426208496s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.076957702636719e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for CLaSSES took 5.291148662567139s
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.0006363391876220703s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2661323547363281s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.021528959274291992s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.600120544433594e-05s
Believability | Calculation of trust value for Temples of the Classical World took 7.867813110351562e-06s
INFO | --- Analysis for classical_temples took 4.041904449462891s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 2.02758526802063s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.24872446060180664s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.177757263183594e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 4.291534423828125e-06s
INFO | --- Analysis for clean-energy-data-reegle took 8.828081846237183s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.27056884765625s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.843971252441406e-05s
Believability | Calculation of trust value for CLLD-afbo took 3.3855438232421875e-05s
INFO | --- Analysis for clld-afbo took 3.4481067657470703s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.124641418457031e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0012924671173095703s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.26657986640930176s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.724761962890625e-05s
Believability | Calculation of trust value for CLLD-APICS took 8.106231689453125e-06s
INFO | --- Analysis for clld-apics took 3.4302804470062256s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2564198970794678s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.814697265625e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 5.9604644775390625e-06s
INFO | --- Analysis for clld-ewave took 3.3603219985961914s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.5299530029296875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.26882290840148926s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020975112915039062s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010704994201660156s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 7.62939453125e-06s
INFO | --- Analysis for clld-glottolog took 4.177596807479858s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.482269287109375e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2720065116882324s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.296966552734375e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.9141387939453125e-06s
INFO | --- Analysis for clld-phoible took 3.503777027130127s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0012922286987304688s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.25742673873901367s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.03176093101501465s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0015363693237304688s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 0.00011658668518066406s
Believability | Calculation of trust value for CLLD-SAILS took 7.62939453125e-06s
INFO | --- Analysis for clld-sails took 3.608214855194092s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.25699424743652344s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.177757263183594e-05s
Believability | Calculation of trust value for CLLD-WALS took 6.67572021484375e-06s
INFO | --- Analysis for clld-wals took 3.525026559829712s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.1961669921875e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.2596888542175293s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.7738037109375e-05s
Believability | Calculation of trust value for CLLD-WOLD took 8.106231689453125e-06s
INFO | --- Analysis for clld-wold took 3.4382264614105225s
Availability | SPARQL endpoint availability check for COD inventory took 4.1961669921875e-05s
Availability | VoID file availability check for COD inventory took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for COD inventory took 0.2703268527984619s
Reputation | Calculation of the PageRank for COD inventory took 0.021139860153198242s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.4809112548828125e-05s
Believability | Calculation of trust value for COD inventory took 8.821487426757812e-06s
INFO | --- Analysis for cod-inventory took 2.859720230102539s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.14577245712280273s
Availability | VoID file availability check for Cooperation Databank took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.26815128326416016s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02074408531188965s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.647804260253906e-05s
Believability | Calculation of trust value for Cooperation Databank took 7.867813110351562e-06s
INFO | --- Analysis for CoDa took 2.523142099380493s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.029273986816406e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.2555551528930664s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.075599670410156e-05s
Believability | Calculation of trust value for CODE Endpoint took 7.3909759521484375e-06s
INFO | --- Analysis for code-endpoint took 2.8983075618743896s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.6020300388336182s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.25972509384155273s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.504753112792969e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 1.3113021850585938e-05s
INFO | --- Analysis for coins-openuplabs took 3.0183684825897217s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.3787083625793457s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.28179001808166504s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 3.457069396972656e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0009610652923583984s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 0.00010395050048828125s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.239776611328125e-05s
INFO | --- Analysis for CoLChina_sp2000 took 7.18875789642334s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.06425595283508301s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.24818086624145508s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.6716461181640625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for colinda took 2.4891769886016846s
Availability | SPARQL endpoint availability check for CN  2012 took 26.494410276412964s
Availability | VoID file availability check for CN  2012 took 0.0007581710815429688s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.253190279006958s
Reputation | Calculation of the PageRank for CN  2012 took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.38690185546875e-05s
Believability | Calculation of trust value for CN  2012 took 6.198883056640625e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 126.67570567131042s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.100799560546875e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.000244140625s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.2506449222564697s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.62939453125e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 2.915937662124634s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.172325134277344e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2505834102630615s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.218650817871094e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 8.106231689453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.9259345531463623s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.887580871582031e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.6961309909820557s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02106499671936035s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.0517578125e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 6.67572021484375e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 3.3932247161865234s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 7.867813110351562e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2584712505340576s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 3.24249267578125e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 7.62939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.899888277053833s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.124641418457031e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.26605701446533203s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 2.956390380859375e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 6.4373016357421875e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.9148008823394775s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.3362562656402588s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2626221179962158s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 5.2928924560546875e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for CompHistSem took 3.769477128982544s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.248816967010498s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2742154598236084s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020814180374145508s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.814697265625e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 7.152557373046875e-06s
INFO | --- Analysis for comsode-d3-2 took 7.6363654136657715s
Availability | SPARQL endpoint availability check for ConceptNet took 4.220008850097656e-05s
Availability | VoID file availability check for ConceptNet took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.24991774559020996s
Reputation | Calculation of the PageRank for ConceptNet took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.24249267578125e-05s
Believability | Calculation of trust value for ConceptNet took 7.867813110351562e-06s
INFO | --- Analysis for conceptnet took 2.8161513805389404s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.267692565917969e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2697153091430664s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.606910705566406e-05s
Believability | Calculation of trust value for 2011 US Congress People took 5.245208740234375e-06s
INFO | --- Analysis for congresspeople took 2.896418809890747s
Availability | SPARQL endpoint availability check for MIMO took 0.32324719429016113s
Availability | VoID file availability check for MIMO took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for MIMO took 0.2765066623687744s
Reputation | Calculation of the PageRank for MIMO took 0.020977258682250977s
Interlinking | Calculation of Degree of Connection for MIMO took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0010561943054199219s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.33514404296875e-05s
Believability | Calculation of trust value for MIMO took 7.867813110351562e-06s
INFO | --- Analysis for CONNECTED took 3.6887154579162598s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.26723313331604004s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 8.106231689453125e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.909268856048584s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.172325134277344e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.24113702774047852s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.021013259887695312s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.170967102050781e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 7.62939453125e-06s
INFO | --- Analysis for copac-library-catalogue took 2.936551809310913s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.220008850097656e-05s
Availability | VoID file availability check for Copyright Free Music took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.26917433738708496s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.528594970703125e-05s
Believability | Calculation of trust value for Copyright Free Music took 7.152557373046875e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.7555623054504395s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 5.2928924560546875e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.2581484317779541s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.605552673339844e-05s
Believability | Calculation of trust value for CopyrightTermBank took 6.9141387939453125e-06s
INFO | --- Analysis for copyrighttermbank took 34.23924922943115s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.6739625930786133s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2485675811767578s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.029273986816406e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 7.3909759521484375e-06s
INFO | --- Analysis for core took 6.4587366580963135s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.7453804016113281s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002906322479248047s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 116.68403625488281s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9182534217834473s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 8.568451404571533s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.64124584197998s
Versatility | Languages check for Corine linked dataset @PSNC took 300.1695692539215s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 3.1665639877319336s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.2787492275238037s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 12.044886350631714s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.27863430976867676s
License | MR license check for Corine linked dataset @PSNC took 0.5105087757110596s
License | HR license check for Corine linked dataset @PSNC took 300.2345349788666s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.3297743797302246s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.2384226322174072s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.5588843822479248s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.41330718994140625s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.2179579734802246s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.2569003105163574s
Performance | Throughput check for Corine linked dataset @PSNC took 11.588688373565674s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.319450378417969e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.21340465545654297s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.20112347602844238s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4337952136993408s
Interlinking | skos check for Corine linked dataset @PSNC took 0.443347692489624s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.171515464782715s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5021340847015381s
Currency | Modification date check for Corine linked dataset @PSNC took 0.23746132850646973s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 152.38418221473694s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.21409893035888672s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.3233928680419922s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.34142494201660156s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 43.35375475883484s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6615002155303955s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.66402268409729s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.2845311164855957s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 82.8030846118927s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.44173526763916s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 37.35289549827576s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.3645117282867432s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 84.61362075805664s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.735567569732666s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.6695053577423096s
Security | Sign check for Corine linked dataset @PSNC took 0.9421663284301758s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 16.28563928604126s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 2.1079132556915283s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 1.4009108543395996s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 0.01727914810180664s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.027983665466308594s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 0.021080970764160156s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 0.00027251243591308594s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.4543533325195312e-05s
INFO | --- Analysis for Corine_linked_dataset took 2901.491456747055s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.987022399902344e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.00021719932556152344s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.2643136978149414s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.021206378936767578s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.314018249511719e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.3909759521484375e-06s
INFO | --- Analysis for corn took 4.228217601776123s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.1484832763671875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2567257881164551s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.02086186408996582s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.123283386230469e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 7.62939453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 3.275522470474243s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.839897155761719e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.23872780799865723s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.147125244140625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 6.198883056640625e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 3.2904536724090576s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.5299530029296875e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.26393747329711914s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.961822509765625e-05s
Believability | Calculation of trust value for Cornetto1.2 took 8.344650268554688e-06s
INFO | --- Analysis for cornetto took 13.801045417785645s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.17925715446472168s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005004405975341797s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 97.26406335830688s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6480236053466797s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 97.71781873703003s
Interoperability | New terms check for Corporate Body Named Authority List  took 91.54286670684814s
Versatility | Languages check for Corporate Body Named Authority List  took 300.1320059299469s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 3.2021217346191406s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.34792351722717285s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.4123189449310303s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 3.2876715660095215s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.30201005935668945s
License | MR license check for Corporate Body Named Authority List  took 0.2642996311187744s
License | HR license check for Corporate Body Named Authority List  took 300.0564887523651s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.18283867835998535s
Understandability | Number of label check for Corporate Body Named Authority List  took 5.855915307998657s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.25609421730041504s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.1049048900604248s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.22085213661193848s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.17768645286560059s
Performance | Throughput check for Corporate Body Named Authority List  took 10.874255657196045s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 0.000110626220703125s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.2489457130432129s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 9.987052917480469s
Interlinking | skos check for Corporate Body Named Authority List  took 0.2493128776550293s
Interlinking | skos check for Corporate Body Named Authority List  took 0.29239487648010254s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.30104804039001465s
Currency | Creation date check for Corporate Body Named Authority List  took 0.7128927707672119s
Currency | Modification date check for Corporate Body Named Authority List  took 0.20569920539855957s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 520.4530119895935s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.18563342094421387s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.20743703842163086s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.17989444732666016s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 30.87366557121277s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.133310556411743s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6095943450927734s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.15965485572814941s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4893248081207s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.457834959030151s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 42.38084673881531s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.549440622329712s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.42735052108765s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.1231517791748047s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.4053764343261719s
Security | Sign check for Corporate Body Named Authority List  took 0.13320326805114746s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 4.336355209350586s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.5646564960479736s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.07075071334838867s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.316734313964844e-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 8.344650268554688e-06s
INFO | --- Analysis for corporate-body took 15366.352311134338s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.6348001956939697s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.6892986297607422s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 8.58306884765625e-06s
INFO | --- Analysis for CorpusFibonacci took 6.208704948425293s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.1961669921875e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.32881951332092285s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.021904706954956055s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0008313655853271484s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.504753112792969e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for corscheck took 4.817649602890015s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.1415548324584961s
Availability | VoID file availability check for Country Name Authority List took 0.0006818771362304688s
Extra | Recovery of all triples for Country Name Authority List took 94.50820708274841s
Performance | Total latancy measurement for Country Name Authority List took 0.6184713840484619s
Amount of data | Number of triples check for Country Name Authority List took 87.49838066101074s
Interoperability | New terms check for Country Name Authority List took 107.93885707855225s
Versatility | Languages check for Country Name Authority List took 300.10611844062805s
Interpretability | Number of blank nodes check for Country Name Authority List took 2.948467493057251s
Security | Check HTTPS for Country Name Authority List took 0.22122573852539062s
Interpretability | RDF structures check for Country Name Authority List took 0.4409618377685547s
Versatility | Serialization formats check for Country Name Authority List took 4.429145336151123s
Availability | RDF dump link check for Country Name Authority List took 0.21558237075805664s
License | MR license check for Country Name Authority List took 0.15375089645385742s
License | HR license check for Country Name Authority List took 300.0378499031067s
Amount of data | Number of property check for Country Name Authority List took 0.17629551887512207s
Understandability | Number of label check for Country Name Authority List took 12.71134328842163s
Understandability | URI regex check for Country Name Authority List took 0.23273658752441406s
Understandability | Vocabs check for Country Name Authority List took 0.09952402114868164s
Verifiability | Authors check for Country Name Authority List took 0.13972163200378418s
Verifiability | Publishers check for Country Name Authority List took 0.2333366870880127s
Performance | Throughput check for Country Name Authority List took 10.558156251907349s
Amount of data | Check the number of entities for Country Name Authority List took 7.534027099609375e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.282167911529541s
Interlinking | sameAs chians check for Country Name Authority List took 92.80918884277344s
Interlinking | skos check for Country Name Authority List took 0.3175537586212158s
Interlinking | skos check for Country Name Authority List took 0.4718635082244873s
Timeliness | dataset update frequency check for Country Name Authority List took 0.19921064376831055s
Currency | Creation date check for Country Name Authority List took 0.5235705375671387s
Currency | Modification date check for Country Name Authority List took 0.2804830074310303s
Rep.Conc. | URIs length for Country Name Authority List took 605.5647597312927s
Interoperability | New vocabularies check for Country Name Authority List took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.19274282455444336s
Accuracy | Check Functional Property for Country Name Authority List took 0.200150728225708s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.16936278343200684s
Accuracy | Check Empty annotation labels for Country Name Authority List took 29.59413766860962s
Accuracy | Check White space in annotation for Country Name Authority List took 3.1010901927948s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.580275774002075s
Consistency | Disjoint class check for Country Name Authority List took 0.12232780456542969s
Consistency | Check Misplaced properties for Country Name Authority List took 300.43303656578064s
Consistency | Misplaced classes for Country Name Authority List took 8.491194248199463s
Consistency | Check Ontology hijacking for Country Name Authority List took 30.674368143081665s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 10.665964126586914s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.4667670726776s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.0661532878875732s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4095308780670166s
Security | Sign check for Country Name Authority List took 0.14968228340148926s
Availability | Check URIs Dereferenciability for Country Name Authority List took 4.424973726272583s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.1356761455535889s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.028922080993652344s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0009715557098388672s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 2.1457672119140625e-06s
Believability | Calculation of trust value for Country Name Authority List took 8.106231689453125e-06s
INFO | --- Analysis for country-authority-list took 15288.654108285904s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.08621883392333984s
Availability | VoID file availability check for Courts thesaurus took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.26400160789489746s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.794929504394531e-05s
Believability | Calculation of trust value for Courts thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for courts-thesaurus took 4.279613256454468s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.741724967956543s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0003838539123535156s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2497708797454834s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.724761962890625e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 7.152557373046875e-06s
INFO | --- Analysis for Covid-on-the-Web took 7.2700114250183105s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.565763235092163s
Availability | VoID file availability check for CPA 2008 took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.2463700771331787s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.314018249511719e-05s
Believability | Calculation of trust value for CPA 2008 took 5.0067901611328125e-06s
INFO | --- Analysis for cpa-2008 took 125.1117947101593s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.4134519100189209s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0006625652313232422s
Extra | Recovery of all triples for Cooperative Patent Classification took 44.951390504837036s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.0051953792572021s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.2459065914154s
Versatility | Languages check for Cooperative Patent Classification took 120.09130620956421s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.27028846740723s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.22929167747497559s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.19998502731323242s
Availability | RDF dump link check for Cooperative Patent Classification took 0.17735981941223145s
License | MR license check for Cooperative Patent Classification took 0.16477489471435547s
License | HR license check for Cooperative Patent Classification took 90.22476887702942s
Amount of data | Number of property check for Cooperative Patent Classification took 0.22758936882019043s
Understandability | Number of label check for Cooperative Patent Classification took 90.24141716957092s
Understandability | URI regex check for Cooperative Patent Classification took 0.4742166996002197s
Understandability | Vocabs check for Cooperative Patent Classification took 0.23232150077819824s
Verifiability | Authors check for Cooperative Patent Classification took 0.205857515335083s
Verifiability | Publishers check for Cooperative Patent Classification took 0.20714902877807617s
Performance | Throughput check for Cooperative Patent Classification took 10.672036409378052s
Amount of data | Check the number of entities for Cooperative Patent Classification took 8.106231689453125e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.15777802467346191s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.17267107963562012s
Interlinking | skos check for Cooperative Patent Classification took 0.2720649242401123s
Interlinking | skos check for Cooperative Patent Classification took 0.20280957221984863s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.3749992847442627s
Currency | Creation date check for Cooperative Patent Classification took 0.4546220302581787s
Currency | Modification date check for Cooperative Patent Classification took 0.38846445083618164s
Rep.Conc. | URIs length for Cooperative Patent Classification took 155.3641037940979s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.1743311882019043s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 17.212262630462646s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9840617179870605s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.9841272830963135s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.15884113311767578s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.39143538475037s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 23.08432912826538s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.5921216011047363s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.59809017181396s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8483476638793945s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.37142515182495117s
Security | Sign check for Cooperative Patent Classification took 0.23500633239746094s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.5940489768981934s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.6502275466918945s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.027180910110473633s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.054473876953125e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 5.245208740234375e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 7.867813110351562e-06s
INFO | --- Analysis for CPC took 1314.6335990428925s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.214497804641724s
Availability | VoID file availability check for CPC 2008 took 0.0008246898651123047s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.2920212745666504s
Reputation | Calculation of the PageRank for CPC 2008 took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.363059997558594e-05s
Believability | Calculation of trust value for CPC 2008 took 7.62939453125e-06s
INFO | --- Analysis for cpc-2008 took 126.42464423179626s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.44595956802368s
Availability | VoID file availability check for CPV  2003 took 0.0008816719055175781s
Completeness | Calculation of interlinking completeness for CPV  2003 took 1.2518141269683838s
Reputation | Calculation of the PageRank for CPV  2003 took 0.021107196807861328s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.719329833984375e-05s
Believability | Calculation of trust value for CPV  2003 took 5.4836273193359375e-06s
INFO | --- Analysis for cpv-2003 took 117.3626492023468s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.348466157913208s
Availability | VoID file availability check for CPV 2008 took 0.0009257793426513672s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.7107326984405518s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.792213439941406e-05s
Believability | Calculation of trust value for CPV 2008 took 1.0013580322265625e-05s
INFO | --- Analysis for cpv-2008 took 125.52191042900085s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.8237693309784s
Availability | VoID file availability check for crowdsourcing-fb took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.7020635604858398s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 3.886222839355469e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 8.106231689453125e-06s
INFO | --- Analysis for crowdsourcing-fb took 539.297039270401s
Availability | SPARQL endpoint availability check for CRTM took 5.0067901611328125e-05s
Availability | VoID file availability check for CRTM took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for CRTM took 0.7136039733886719s
Reputation | Calculation of the PageRank for CRTM took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.3855438232421875e-05s
Believability | Calculation of trust value for CRTM took 1.239776611328125e-05s
INFO | --- Analysis for crtm took 5.324435710906982s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.172325134277344e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.2765920162200928s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 4.410743713378906e-05s
INFO | --- Analysis for crystal-eye took 4.488745450973511s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.934600830078125s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.3118255138397217s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 5.054473876953125e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 5.245208740234375e-06s
INFO | --- Analysis for ctic-public-dataset took 46.01291537284851s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.076957702636719e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.2772397994995117s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0008370876312255859s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.1948089599609375e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.867813110351562e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.096787214279175s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 20.424691200256348s
Availability | VoID file availability check for CulturaLinkedData took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.3120241165161133s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 2.956390380859375e-05s
Believability | Calculation of trust value for CulturaLinkedData took 7.3909759521484375e-06s
INFO | --- Analysis for culturalinkeddata took 53.789841413497925s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2441389560699463s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2735412120819092s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.62396240234375e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ares-or took 3.0274131298065186s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11989831924438477s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.2671778202056885s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.62396240234375e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.245208740234375e-06s
INFO | --- Analysis for cz-ares-rzp took 2.8796982765197754s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.12946462631225586s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.27640199661254883s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.409385681152344e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 5.4836273193359375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 4.381190299987793s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.12062311172485352s
Availability | VoID file availability check for Integrated pollution registry took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.73341965675354s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.886222839355469e-05s
Believability | Calculation of trust value for Integrated pollution registry took 5.7220458984375e-06s
INFO | --- Analysis for cz-cenia-pollution took 3.824103593826294s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.12221813201904297s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.28563475608825684s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020905494689941406s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 4.00543212890625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.245208740234375e-06s
INFO | --- Analysis for cz-contracts took 2.9295547008514404s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.1484832763671875e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.2794663906097412s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.075599670410156e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-courts took 3.0683488845825195s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.11933517456054688s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.28412389755249023s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.504753112792969e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 6.4373016357421875e-06s
INFO | --- Analysis for cz-ctia-bans took 5.146795034408569s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.12474298477172852s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2767503261566162s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.314018249511719e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.892350435256958s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.1217336654663086s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.28070855140686035s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.6716461181640625e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-focus took 2.887284517288208s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.11972498893737793s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007889270782470703s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.280153751373291s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020694255828857422s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.744529724121094e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 7.867813110351562e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.9686663150787354s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.12119579315185547s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.27355074882507324s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0008299350738525391s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.814697265625e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.825104713439941s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 10.263420104980469s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.001093149185180664s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.2870290279388428s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02097773551940918s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.076957702636719e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 1.6927719116210938e-05s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 23.086403846740723s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 10.124508619308472s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.28093767166137695s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020647287368774414s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.528594970703125e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 5.4836273193359375e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 22.980480194091797s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.8059382438659668s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.28026318550109863s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.00543212890625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.925306558609009s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.4440145492553711s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0011022090911865234s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.2823348045349121s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.48754620552063s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.39816737174987793s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.2916088104248047s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0211484432220459s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0010251998901367188s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.8160552978515625e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.501528024673462s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.41809988021850586s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2784395217895508s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.468658447265625s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.41819047927856445s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.001032114028930664s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.29811716079711914s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.0220947265625s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.503448724746704s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.46642065048217773s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0008137226104736328s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2769451141357422s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.528594970703125e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 6.198883056640625e-06s
INFO | --- Analysis for cz-czso-regions took 3.260418176651001s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.49819278717041016s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2814760208129883s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.6637110710144043s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.48090171813964844s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.29237866401672363s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007600784301757812s
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 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.658782482147217s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.4016439914703369s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.27798008918762207s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.5204968452453613s
Availability | SPARQL endpoint availability check for ATC groups took 0.12047362327575684s
Availability | VoID file availability check for ATC groups took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for ATC groups took 0.29454898834228516s
Reputation | Calculation of the PageRank for ATC groups took 0.020836830139160156s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.128715515136719e-05s
Believability | Calculation of trust value for ATC groups took 7.3909759521484375e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.9329171180725098s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.12023282051086426s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.29062557220458984s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0251998901367188e-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.504753112792969e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.7220458984375e-06s
INFO | --- Analysis for cz-fulfillments took 2.8855857849121094s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.026635169982910156s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.29523181915283203s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.021119117736816406s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 5.054473876953125e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ic took 3.737966299057007s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.24878907203674316s
Availability | VoID file availability check for List of Czech data boxes took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.2682821750640869s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of Czech data boxes took 4.76837158203125e-06s
INFO | --- Analysis for cz-list-of-databoxes took 4.543456315994263s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.25002121925354004s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.292971134185791s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020255327224731445s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.0067901611328125e-06s
INFO | --- Analysis for cz-nace took 4.522449493408203s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.31305766105651855s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005807876586914062s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 150.96339511871338s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8519742488861084s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.26412200927734375s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.629594087600708s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 27.66989827156067s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4562110900878906s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18767070770263672s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.616126775741577s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3534984588623047s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4494028091430664s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.7166893482208252s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16093158721923828s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.9683432579040527s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.31685781478881836s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17995619773864746s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21097111701965332s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24146628379821777s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.959586143493652s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.295608520507812e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17643356323242188s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.22151732444763184s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3754258155822754s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16286301612854004s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.72715163230896s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5866973400115967s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3599209785461426s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 55.55999970436096s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16147208213806152s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1709885597229004s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.19475841522216797s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 45.94724750518799s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.4321541786193848s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6212854385375977s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20761966705322266s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.9114301204681396s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.541150331497192s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 99.50229907035828s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7697641849517822s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.149493455886841s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.107928991317749s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20838570594787598s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.44739723205566406s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1026.32492685318s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7087509632110596s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0221102237701416s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.24249267578125e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.9073486328125e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.9604644775390625e-06s
INFO | --- Analysis for cz-nkod took 67345.21559667587s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.2243046760559082s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.7386572360992432s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.62396240234375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.4836273193359375e-06s
INFO | --- Analysis for cz-orders took 5.215503215789795s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.19932031631469727s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0013251304626464844s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 258.07606983184814s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.6550719738006592s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 17.3421528339386s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 18.556679248809814s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.18362855911255s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 2.997493267059326s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.5538740158081055s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.6010501384735107s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 35.70928478240967s
License | MR license check for Institutions of public power of the Czech Republic took 0.6402847766876221s
License | HR license check for Institutions of public power of the Czech Republic took 300.15454149246216s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.2561366558074951s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 6.373882293701172s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4852728843688965s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.2856254577636719s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.5919618606567383s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.2032616138458252s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.597370147705078s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.067258596420288s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.3294486999511719s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.8239269256591797s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.263012170791626s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11573672294616699s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.25102853775024414s
Currency | Creation date check for Institutions of public power of the Czech Republic took 1.0250160694122314s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.33527469635009766s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 210.53557324409485s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 125.46855306625366s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.49051332473754883s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.14244985580444336s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.14976191520690918s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 86.93771624565125s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0790984630584717s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.630352020263672s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.20703530311584473s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 88.17341804504395s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 8.73732304573059s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 76.71712899208069s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.4243464469909668s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 76.05527424812317s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.9003729820251465s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.9220824241638184s
Security | Sign check for Institutions of public power of the Czech Republic took 0.12953901290893555s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 472.856906414032s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 1.428074836730957s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.02182912826538086s
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.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 84.96857237815857s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ovm took 2629.3294105529785s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.11686873435974121s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.30115604400634766s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 1.1205673217773438e-05s
INFO | --- Analysis for cz-ovm-agendas took 4.135937452316284s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 20.002269506454468s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.728229284286499s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.866455078125e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ruian took 114.6717278957367s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.5030436515808105s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.2678360939025879s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.02077960968017578s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.700920104980469e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 3.7217893600463867s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.500455379486084s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.7126753330230713s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.021206140518188477s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-sao-check-actions took 4.53076434135437s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4944338798522949s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.26022839546203613s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.0040740966796875e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 2.3126602172851562e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 3.5153591632843018s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10470128059387207s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.7292232513427734s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.337860107421875e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.225064992904663s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10700440406799316s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2871992588043213s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.2901763916015625e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.763399600982666s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.10756945610046387s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2775843143463135s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.552436828613281e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.7905445098876953s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.12679028511047363s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005779266357421875s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 253.38911533355713s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5731689929962158s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 14.251001834869385s
Interoperability | New terms check for Summary types of Czech institutions of public power took 15.597003936767578s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.129025220871s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 3.5769402980804443s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.1620161533355713s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.39400744438171387s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 34.7026309967041s
License | MR license check for Summary types of Czech institutions of public power took 0.10880589485168457s
License | HR license check for Summary types of Czech institutions of public power took 300.1180896759033s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.27184367179870605s
Understandability | Number of label check for Summary types of Czech institutions of public power took 3.003629684448242s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.26317286491394043s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.1620619297027588s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.24935507774353027s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.18295574188232422s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.55875539779663s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.0978896617889404s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.15056204795837402s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.6851022243499756s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.10236144065856934s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.09980249404907227s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.17812085151672363s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.3042893409729004s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.16220378875732422s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 206.01760077476501s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 158.49306273460388s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.5442671775817871s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.10934209823608398s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.13296937942504883s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 85.31758093833923s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0855422019958496s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.613459587097168s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.16294074058532715s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 87.25597596168518s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 8.75080418586731s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 79.54454016685486s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.3310458660125732s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 75.88484120368958s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.9279284477233887s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.9745383262634277s
Security | Sign check for Summary types of Czech institutions of public power took 0.1155400276184082s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 490.87430238723755s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.1519713401794434s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.022391796112060547s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.600120544433594e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 43.27381491661072s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.0967254638671875e-05s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2629.7902233600616s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.104400634765625s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0004017353057861328s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.6918551921844482s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 4.1484832763671875e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 4.036574125289917s
Availability | SPARQL endpoint availability check for State funding providers took 0.10533380508422852s
Availability | VoID file availability check for State funding providers took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for State funding providers took 0.7248318195343018s
Reputation | Calculation of the PageRank for State funding providers took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.8623809814453125e-05s
Believability | Calculation of trust value for State funding providers took 6.4373016357421875e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.665907621383667s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11322569847106934s
Availability | VoID file availability check for Organizations active in R&D took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2594771385192871s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.719329833984375e-05s
Believability | Calculation of trust value for Organizations active in R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.4343721866607666s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11269688606262207s
Availability | VoID file availability check for R&D Programmes took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2707550525665283s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 4.0531158447265625e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.172325134277344e-05s
Believability | Calculation of trust value for R&D Programmes took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.2182531356811523s
Availability | SPARQL endpoint availability check for R&D Projects took 0.10503578186035156s
Availability | VoID file availability check for R&D Projects took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2660539150238037s
Reputation | Calculation of the PageRank for R&D Projects took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.981590270996094e-05s
Believability | Calculation of trust value for R&D Projects took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-projects took 3.2089438438415527s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11350727081298828s
Availability | VoID file availability check for Institutional research plans took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.2624061107635498s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.1961669921875e-05s
Believability | Calculation of trust value for Institutional research plans took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.802149534225464s
Availability | SPARQL endpoint availability check for Results of R&D took 0.10571026802062988s
Availability | VoID file availability check for Results of R&D took 0.0007996559143066406s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.2664148807525635s
Reputation | Calculation of the PageRank for Results of R&D took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.0531158447265625e-05s
Believability | Calculation of trust value for Results of R&D took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-results took 2.758375406265259s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10958647727966309s
Availability | VoID file availability check for Tenders in R&D took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2554469108581543s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020910024642944336s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.933906555175781e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.734931230545044s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.363059997558594e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.29155731201171875s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020811796188354492s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.24249267578125e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.2874603271484375e-05s
INFO | --- Analysis for czech_addresses took 4.440774440765381s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 180.50411248207092s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.27091526985168457s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020684003829956055s
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.0007436275482177734s
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.239776611328125e-05s
INFO | --- Analysis for DanteLatinLoanwords took 314.3153212070465s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.609166145324707s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006687641143798828s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 144.4787962436676s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.029003381729126s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 8.84006953239441s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 3.9750571250915527s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.31973052024841s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.6334481239318848s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.21448063850402832s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 1.1508970260620117s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 1.4404115676879883s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.3797130584716797s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.5348882675170898s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 61.787163734436035s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.25754475593566895s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.947782039642334s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.5398023128509521s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.23613190650939941s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.2658882141113281s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2319498062133789s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.299985885620117s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.152557373046875e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.22701549530029297s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.38794374465942383s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.7764573097229004s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.5794229507446289s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2713911533355713s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.8541209697723389s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.6915926933288574s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 83.1125340461731s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2573540210723877s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.8525075912475586s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.4768822193145752s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 42.785109758377075s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.202901601791382s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.769888401031494s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.5945649147033691s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.064837217330933s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.566342115402222s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 48.6008403301239s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.464897632598877s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.092381477355957s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8868916034698486s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2688114643096924s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.26383352279663086s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 10.99063515663147s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.8749735355377197s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02097797393798828s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00013875961303710938s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.9073486328125e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 7.62939453125e-06s
INFO | --- Analysis for data-bnf-fr took 783.5863819122314s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.11422157287597656s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0002608299255371094s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.6386568546295166s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.2947986125946045s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 6.834848880767822s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.2024803161621094s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.11409878730773926s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.5659339427947998s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.038450002670288086s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.10190749168395996s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.09053707122802734s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.08516860008239746s
License | MR license check for Open Data from the Italian National Research Council took 0.09347987174987793s
License | HR license check for Open Data from the Italian National Research Council took 11.632990837097168s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.08958601951599121s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.8249831199645996s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.17608070373535156s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.15689349174499512s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.09836387634277344s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.08757472038269043s
Performance | Throughput check for Open Data from the Italian National Research Council took 12.240365982055664s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 6.914138793945312e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.08557987213134766s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.0857536792755127s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.09909605979919434s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.05589914321899414s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.08810663223266602s
Currency | Creation date check for Open Data from the Italian National Research Council took 2.9624669551849365s
Currency | Modification date check for Open Data from the Italian National Research Council took 3.5579705238342285s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 15.59631633758545s
Interoperability | New vocabularies check for Open Data from the Italian National Research Council took 24.728907346725464s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.08633303642272949s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.08208537101745605s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.08074188232421875s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.5351331233978271s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.03205466270446777s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.026973724365234375s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.0866546630859375s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.201812267303467s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.2041168212890625s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.5405280590057373s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.3174724578857422s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 12.269025087356567s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03303670883178711s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.10742712020874023s
Security | Sign check for Open Data from the Italian National Research Council took 0.08620142936706543s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 638.0913214683533s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 1.433480978012085s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.021795034408569336s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 0.00012159347534179688s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 37.879106283187866s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.245208740234375e-06s
INFO | --- Analysis for data-cnr-it took 814.3137509822845s
Availability | SPARQL endpoint availability check for Data.gov took 1.4318146705627441s
Availability | VoID file availability check for Data.gov took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for Data.gov took 0.2611672878265381s
Reputation | Calculation of the PageRank for Data.gov took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.218650817871094e-05s
Believability | Calculation of trust value for Data.gov took 6.198883056640625e-06s
INFO | --- Analysis for data-gov took 19.35597038269043s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.16256332397460938s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.7802739143371582s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.128715515136719e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 5.0067901611328125e-06s
INFO | --- Analysis for data-gov-ie took 6.01001763343811s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 6.67572021484375e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.26879072189331055s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.128715515136719e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 4.76837158203125e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.8981688022613525s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.82209038734436s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0008573532104492188s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.7276146411895752s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.021001815795898438s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.604194641113281e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 7.867813110351562e-06s
INFO | --- Analysis for data-hnm-hu took 166.66211342811584s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.13218426704406738s
Availability | VoID file availability check for Climb Dataincubator took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.24239587783813477s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02070450782775879s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.605552673339844e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-climb took 3.436617612838745s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2520937919616699s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.393692016601562e-05s
Believability | Calculation of trust value for Discogs in RDF took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-discogs took 6.563680171966553s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.0508573055267334s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2712066173553467s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.412101745605469e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 5.9604644775390625e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.926495552062988s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.05657315254211426s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.24867606163024902s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 9.441375732421875e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-moseley took 8.935643672943115s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.0635225772857666s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.2691514492034912s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020900487899780273s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.226799011230469e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.239776611328125e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.482309103012085s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.772794485092163s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0007681846618652344s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2499253749847412s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.440017700195312e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 5.0067901611328125e-06s
INFO | --- Analysis for data-incubator-nasa took 7.971322774887085s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.06683897972106934s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2602112293243408s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.021136760711669922s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 8.058547973632812e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.4399471282958984s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.061165809631347656s
Availability | VoID file availability check for Pokedex data in RDF took 0.0007948875427246094s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.26160573959350586s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.822845458984375e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.191879034042358s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0571293830871582s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.2684764862060547s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.250640869140625e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.0013580322265625e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.4991049766540527s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.7629480361938477s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006747245788574219s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 66.55164527893066s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.3056714534759521s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 0.2819969654083252s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5109379291534424s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 9.827419996261597s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 0.2899026870727539s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.13575434684753418s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.30576229095458984s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.31688833236694336s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.2766764163970947s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.30135655403137207s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 3.0216031074523926s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.28034114837646484s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 0.4499094486236572s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.5863919258117676s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.3393900394439697s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.3331468105316162s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.310133695602417s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 10.807448863983154s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 6.222724914550781e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.2943413257598877s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.28171706199645996s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.35323238372802734s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.3003871440887451s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.30548572540283203s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.6208062171936035s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.5944879055023193s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 59.76238203048706s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.2892277240753174s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2803936004638672s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.2846200466156006s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 38.194223165512085s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.147855043411255s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.2973318099975586s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.8875617980957031s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 20.958534240722656s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.6816039085388184s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.00015687942504882812s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.46086621284484863s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.29285454750061035s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 1790.697219133377s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.6879110336303711s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02169060707092285s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 9.703636169433594e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 4.291534423828125e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 8.106231689453125e-06s
INFO | --- Analysis for data-open-ac-uk took 2095.163293361664s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8811776638031006s
Availability | VoID file availability check for Persée in RDF took 0.0011682510375976562s
Extra | Recovery of all triples for Persée in RDF took 1.773273229598999s
Performance | Total latancy measurement for Persée in RDF took 0.7172904014587402s
Amount of data | Number of triples check for Persée in RDF took 1.1168537139892578s
Interoperability | New terms check for Persée in RDF took 1.7331504821777344s
Versatility | Languages check for Persée in RDF took 120.60080862045288s
Interpretability | Number of blank nodes check for Persée in RDF took 0.47443437576293945s
Interpretability | RDF structures check for Persée in RDF took 0.7707431316375732s
Versatility | Serialization formats check for Persée in RDF took 0.9525313377380371s
Availability | RDF dump link check for Persée in RDF took 0.2881486415863037s
License | MR license check for Persée in RDF took 1.4431557655334473s
License | HR license check for Persée in RDF took 38.22045421600342s
Amount of data | Number of property check for Persée in RDF took 0.13813114166259766s
Understandability | Number of label check for Persée in RDF took 1.8198044300079346s
Understandability | URI regex check for Persée in RDF took 0.8554971218109131s
Understandability | Vocabs check for Persée in RDF took 0.31257152557373047s
Verifiability | Authors check for Persée in RDF took 0.14354848861694336s
Verifiability | Publishers check for Persée in RDF took 0.1353292465209961s
Performance | Throughput check for Persée in RDF took 10.890757322311401s
Amount of data | Check the number of entities for Persée in RDF took 7.534027099609375e-05s
Verifiability | Contribs. check for Persée in RDF took 0.13320064544677734s
Interlinking | sameAs chians check for Persée in RDF took 0.2030773162841797s
Interlinking | skos check for Persée in RDF took 0.7303807735443115s
Interlinking | skos check for Persée in RDF took 0.13273334503173828s
Timeliness | dataset update frequency check for Persée in RDF took 0.6688804626464844s
Currency | Creation date check for Persée in RDF took 0.5532567501068115s
Currency | Modification date check for Persée in RDF took 0.2674562931060791s
Rep.Conc. | URIs length for Persée in RDF took 3.5300848484039307s
Interoperability | New vocabularies check for Persée in RDF took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.1299142837524414s
Accuracy | Check Functional Property for Persée in RDF took 0.1446056365966797s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.12986469268798828s
Accuracy | Check Empty annotation labels for Persée in RDF took 1.0769920349121094s
Accuracy | Check White space in annotation for Persée in RDF took 0.038342952728271484s
Accuracy | Check Datatype consistency for Persée in RDF took 0.029549121856689453s
Consistency | Disjoint class check for Persée in RDF took 0.29424142837524414s
Consistency | Check Misplaced properties for Persée in RDF took 2.6407809257507324s
Consistency | Misplaced classes for Persée in RDF took 0.22866559028625488s
Consistency | Check Ontology hijacking for Persée in RDF took 1.842583179473877s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.204575538635254s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.689323663711548s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.032462120056152344s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.13207721710205078s
Security | Sign check for Persée in RDF took 0.7198045253753662s
Availability | Check URIs Dereferenciability for Persée in RDF took 1338.6227984428406s
Completeness | Calculation of interlinking completeness for Persée in RDF took 1.3425545692443848s
Reputation | Calculation of the PageRank for Persée in RDF took 0.021917104721069336s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.430511474609375e-06s
Believability | Calculation of trust value for Persée in RDF took 1.2636184692382812e-05s
INFO | --- Analysis for data-persee-fr took 1580.8292663097382s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.291534423828125e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00036334991455078125s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.7180318832397461s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.02096247673034668s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.147125244140625e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 7.62939453125e-06s
INFO | --- Analysis for data-southampton-ac-uk took 6.552717685699463s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.8393964767456055s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.27582740783691406s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020909786224365234s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011920928955078125s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 8.106231689453125e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.20742154121399s
Availability | SPARQL endpoint availability check for Open Data Web took 0.2890310287475586s
Availability | VoID file availability check for Open Data Web took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.26396942138671875s
Reputation | Calculation of the PageRank for Open Data Web took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.147125244140625e-05s
Believability | Calculation of trust value for Open Data Web took 8.106231689453125e-06s
INFO | --- Analysis for data.odw.tw took 2.709794282913208s
Availability | SPARQL endpoint availability check for DataFAQs took 4.100799560546875e-05s
Availability | VoID file availability check for DataFAQs took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.2535576820373535s
Reputation | Calculation of the PageRank for DataFAQs took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.24249267578125e-05s
Believability | Calculation of trust value for DataFAQs took 1.0728836059570312e-05s
INFO | --- Analysis for datafaqs took 3.417357921600342s
Availability | SPARQL endpoint availability check for datahub took 4.4345855712890625e-05s
Availability | VoID file availability check for datahub took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for datahub took 0.2838172912597656s
Reputation | Calculation of the PageRank for datahub took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for datahub took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for datahub took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for datahub took 4.76837158203125e-05s
Believability | Calculation of trust value for datahub took 7.152557373046875e-06s
INFO | --- Analysis for datahub took 3.519031524658203s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 5.365078449249268s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.25065112113952637s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.147125244140625e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 7.3909759521484375e-06s
INFO | --- Analysis for datahub-kr-datamap took 15.294754981994629s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3496377468109131s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2722628116607666s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.081031799316406e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.821487426757812e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.498995304107666s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.566813468933105s
Availability | VoID file availability check for datos-artium-org took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.8731307983398438s
Reputation | Calculation of the PageRank for datos-artium-org took 0.021220684051513672s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012111663818359375s
Believability | Calculation of trust value for datos-artium-org took 7.152557373046875e-06s
INFO | --- Analysis for datos-artium-org took 166.34959602355957s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8310565948486328s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006146430969238281s
Extra | Recovery of all triples for Datos.bcn.cl took 89.67062091827393s
Performance | Total latancy measurement for Datos.bcn.cl took 81.22578740119934s
Amount of data | Number of triples check for Datos.bcn.cl took 45.39296817779541s
Interoperability | New terms check for Datos.bcn.cl took 3.663400411605835s
Versatility | Languages check for Datos.bcn.cl took 301.01472640037537s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 2.663832426071167s
Security | Check HTTPS for Datos.bcn.cl took 18.577335119247437s
Interpretability | RDF structures check for Datos.bcn.cl took 20.24765181541443s
Versatility | Serialization formats check for Datos.bcn.cl took 19.80705761909485s
Availability | RDF dump link check for Datos.bcn.cl took 19.994048833847046s
License | MR license check for Datos.bcn.cl took 20.09045433998108s
License | HR license check for Datos.bcn.cl took 37.7074294090271s
Amount of data | Number of property check for Datos.bcn.cl took 2.2460031509399414s
Understandability | Number of label check for Datos.bcn.cl took 20.75643825531006s
Understandability | URI regex check for Datos.bcn.cl took 39.24930715560913s
Understandability | Vocabs check for Datos.bcn.cl took 20.03181004524231s
Verifiability | Authors check for Datos.bcn.cl took 20.009079217910767s
Verifiability | Publishers check for Datos.bcn.cl took 19.986434936523438s
Performance | Throughput check for Datos.bcn.cl took 200.09192776679993s
Amount of data | Check the number of entities for Datos.bcn.cl took 0.00014829635620117188s
Verifiability | Contribs. check for Datos.bcn.cl took 20.017902612686157s
Interlinking | sameAs chians check for Datos.bcn.cl took 19.996180295944214s
Interlinking | skos check for Datos.bcn.cl took 20.035580158233643s
Interlinking | skos check for Datos.bcn.cl took 19.968021631240845s
Timeliness | dataset update frequency check for Datos.bcn.cl took 20.04797339439392s
Currency | Creation date check for Datos.bcn.cl took 39.994070529937744s
Currency | Modification date check for Datos.bcn.cl took 20.015546798706055s
Rep.Conc. | URIs length for Datos.bcn.cl took 87.4546868801117s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2393484115600586s
Accuracy | Check Functional Property for Datos.bcn.cl took 19.985374212265015s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 20.023213148117065s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 42.63001036643982s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.24220895767211914s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2629523277282715s
Consistency | Disjoint class check for Datos.bcn.cl took 1.221994161605835s
Consistency | Check Misplaced properties for Datos.bcn.cl took 44.474181175231934s
Consistency | Misplaced classes for Datos.bcn.cl took 16.449838638305664s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 50.30199599266052s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.2291326522827148s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 6.549483299255371s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.29372692108154297s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 14.662428379058838s
Security | Sign check for Datos.bcn.cl took 19.73392367362976s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 22.659454822540283s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.1329503059387207s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02092909812927246s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 8.0108642578125e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 2.1457672119140625e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.198883056640625e-06s
INFO | --- Analysis for datos-bcn-cl took 3238.968000650406s
Availability | SPARQL endpoint availability check for datos.bne.es took 30.079768657684326s
Availability | VoID file availability check for datos.bne.es took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.7259993553161621s
Reputation | Calculation of the PageRank for datos.bne.es took 0.021263837814331055s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011920928955078125s
Believability | Calculation of trust value for datos.bne.es took 7.152557373046875e-06s
INFO | --- Analysis for datos-bne-es took 116.42724943161011s
Availability | SPARQL endpoint availability check for dbacademic took 0.17094635963439941s
Availability | VoID file availability check for dbacademic took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for dbacademic took 0.28295254707336426s
Reputation | Calculation of the PageRank for dbacademic took 0.0209200382232666s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.24249267578125e-05s
Believability | Calculation of trust value for dbacademic took 5.7220458984375e-06s
INFO | --- Analysis for dbacademic took 3.4558777809143066s
Availability | SPARQL endpoint availability check for DBkWik took 0.21474432945251465s
Availability | VoID file availability check for DBkWik took 0.0006220340728759766s
Extra | Recovery of all triples for DBkWik took 2.3664004802703857s
Performance | Total latancy measurement for DBkWik took 0.45760607719421387s
Amount of data | Number of triples check for DBkWik took 14.611218929290771s
Interoperability | New terms check for DBkWik took 2.1828572750091553s
Versatility | Languages check for DBkWik took 62.12921714782715s
Interpretability | Number of blank nodes check for DBkWik took 84.90233397483826s
Interpretability | RDF structures check for DBkWik took 1.4165325164794922s
Versatility | Serialization formats check for DBkWik took 1.1251893043518066s
Availability | RDF dump link check for DBkWik took 2.9072213172912598s
License | MR license check for DBkWik took 0.38970303535461426s
License | HR license check for DBkWik took 61.74512195587158s
Amount of data | Number of property check for DBkWik took 0.13660526275634766s
Understandability | Number of label check for DBkWik took 2.002495765686035s
Understandability | URI regex check for DBkWik took 0.26184630393981934s
Understandability | Vocabs check for DBkWik took 0.10589432716369629s
Verifiability | Authors check for DBkWik took 0.11181116104125977s
Verifiability | Publishers check for DBkWik took 0.0987708568572998s
Performance | Throughput check for DBkWik took 10.428211688995361s
Amount of data | Check the number of entities for DBkWik took 0.00010848045349121094s
Verifiability | Contribs. check for DBkWik took 0.11438822746276855s
Interlinking | sameAs chians check for DBkWik took 0.3330104351043701s
Interlinking | skos check for DBkWik took 0.3836216926574707s
Interlinking | skos check for DBkWik took 0.08385825157165527s
Timeliness | dataset update frequency check for DBkWik took 0.24138569831848145s
Currency | Creation date check for DBkWik took 0.4607086181640625s
Currency | Modification date check for DBkWik took 0.20664620399475098s
Rep.Conc. | URIs length for DBkWik took 26.680683374404907s
Interoperability | New vocabularies check for DBkWik took 5.271803140640259s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.1119084358215332s
Accuracy | Check Functional Property for DBkWik took 0.2846522331237793s
Accuracy | Check Inverse Functional Property for DBkWik took 0.2605092525482178s
Accuracy | Check Empty annotation labels for DBkWik took 1.2504258155822754s
Accuracy | Check White space in annotation for DBkWik took 0.023225784301757812s
Accuracy | Check Datatype consistency for DBkWik took 0.027586698532104492s
Consistency | Disjoint class check for DBkWik took 0.3189840316772461s
Consistency | Check Misplaced properties for DBkWik took 12.206977367401123s
Consistency | Misplaced classes for DBkWik took 0.8048014640808105s
Consistency | Check Ontology hijacking for DBkWik took 1.779515266418457s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.1535632610321045s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.803670644760132s
Conciseness | Check Extensional conciseness for DBkWik took 0.03626704216003418s
Conciseness | Check Intensional conciseness for DBkWik took 0.92862868309021s
Security | Sign check for DBkWik took 0.2058124542236328s
Availability | Check URIs Dereferenciability for DBkWik took 15.506990432739258s
Completeness | Calculation of interlinking completeness for DBkWik took 0.783867359161377s
Reputation | Calculation of the PageRank for DBkWik took 0.021190404891967773s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for DBkWik took 6.985664367675781e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 20.703582763671875s
Believability | Calculation of trust value for DBkWik took 6.9141387939453125e-06s
INFO | --- Analysis for dbkwik took 1827.9088368415833s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 7.510185241699219e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.7101225852966309s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001163482666015625s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.239776611328125e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 44.427130699157715s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.3963007926940918s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005817413330078125s
Extra | Recovery of all triples for dblp Knowledge Graph took 68.06512308120728s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.8637316226959229s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.14633584022521973s
Interoperability | New terms check for dblp Knowledge Graph took 1.7504770755767822s
Versatility | Languages check for dblp Knowledge Graph took 30.35681128501892s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.1759612560272217s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1321272850036621s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.14546561241149902s
Availability | RDF dump link check for dblp Knowledge Graph took 0.11749148368835449s
License | MR license check for dblp Knowledge Graph took 0.17905569076538086s
License | HR license check for dblp Knowledge Graph took 30.14171075820923s
Amount of data | Number of property check for dblp Knowledge Graph took 0.16234517097473145s
Understandability | Number of label check for dblp Knowledge Graph took 0.5395166873931885s
Understandability | URI regex check for dblp Knowledge Graph took 0.31439661979675293s
Understandability | Vocabs check for dblp Knowledge Graph took 0.14535093307495117s
Verifiability | Authors check for dblp Knowledge Graph took 0.16939115524291992s
Verifiability | Publishers check for dblp Knowledge Graph took 0.17462825775146484s
Performance | Throughput check for dblp Knowledge Graph took 10.64607286453247s
Amount of data | Check the number of entities for dblp Knowledge Graph took 8.034706115722656e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.14621520042419434s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.17019200325012207s
Interlinking | skos check for dblp Knowledge Graph took 0.19522929191589355s
Interlinking | skos check for dblp Knowledge Graph took 0.19671964645385742s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.19011878967285156s
Currency | Creation date check for dblp Knowledge Graph took 0.31639909744262695s
Currency | Modification date check for dblp Knowledge Graph took 0.3496732711791992s
Rep.Conc. | URIs length for dblp Knowledge Graph took 25.399091243743896s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.22118139266967773s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.1779155731201172s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.17039275169372559s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 17.934480667114258s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.0754506587982178s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.16700530052185059s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 2.8691325187683105s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 24.306408882141113s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 1.4082348346710205s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 0.0001544952392578125s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.16941380500793457s
Security | Sign check for dblp Knowledge Graph took 0.13191652297973633s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.830674409866333s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.0013580322265625e-05s
INFO | --- Analysis for dblp-kg took 289.3362157344818s
Availability | SPARQL endpoint availability check for dbnary took 0.32442212104797363s
Availability | VoID file availability check for dbnary took 0.0005395412445068359s
Extra | Recovery of all triples for dbnary took 1.997743844985962s
Performance | Total latancy measurement for dbnary took 0.3788485527038574s
Amount of data | Number of triples check for dbnary took 1.457000970840454s
Interoperability | New terms check for dbnary took 3.6176962852478027s
Versatility | Languages check for dbnary took 60.39555311203003s
Interpretability | Number of blank nodes check for dbnary took 0.774237871170044s
Security | Check HTTPS for dbnary took 0.1646268367767334s
Interpretability | RDF structures check for dbnary took 0.1271214485168457s
Versatility | Serialization formats check for dbnary took 0.2551131248474121s
Availability | RDF dump link check for dbnary took 0.08503603935241699s
License | MR license check for dbnary took 0.15221595764160156s
License | HR license check for dbnary took 61.51883864402771s
Amount of data | Number of property check for dbnary took 0.10359358787536621s
Understandability | Number of label check for dbnary took 0.6441662311553955s
Understandability | URI regex check for dbnary took 0.19220662117004395s
Understandability | Vocabs check for dbnary took 0.21358394622802734s
Verifiability | Authors check for dbnary took 0.07352423667907715s
Verifiability | Publishers check for dbnary took 0.06954836845397949s
Performance | Throughput check for dbnary took 10.446884632110596s
Amount of data | Check the number of entities for dbnary took 7.200241088867188e-05s
Verifiability | Contribs. check for dbnary took 0.07241249084472656s
Interlinking | sameAs chians check for dbnary took 0.10851550102233887s
Interlinking | skos check for dbnary took 0.27472615242004395s
Interlinking | skos check for dbnary took 0.06993269920349121s
Timeliness | dataset update frequency check for dbnary took 0.1250450611114502s
Currency | Creation date check for dbnary took 0.21978974342346191s
Currency | Modification date check for dbnary took 0.1772162914276123s
Rep.Conc. | URIs length for dbnary took 11.638633012771606s
Interoperability | New vocabularies check for dbnary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.08945655822753906s
Accuracy | Check Functional Property for dbnary took 0.16319012641906738s
Accuracy | Check Inverse Functional Property for dbnary took 0.14385652542114258s
Accuracy | Check Empty annotation labels for dbnary took 0.4730207920074463s
Accuracy | Check White space in annotation for dbnary took 0.03048086166381836s
Accuracy | Check Datatype consistency for dbnary took 0.02820563316345215s
Consistency | Disjoint class check for dbnary took 0.09929895401000977s
Consistency | Check Misplaced properties for dbnary took 8.959655523300171s
Consistency | Misplaced classes for dbnary took 0.24010539054870605s
Consistency | Check Ontology hijacking for dbnary took 1.8146731853485107s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.309450387954712s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.09463906288147s
Conciseness | Check Extensional conciseness for dbnary took 0.03216123580932617s
Conciseness | Check Intensional conciseness for dbnary took 0.18101024627685547s
Security | Sign check for dbnary took 0.1423206329345703s
Availability | Check URIs Dereferenciability for dbnary took 11.607994079589844s
Completeness | Calculation of interlinking completeness for dbnary took 0.8159332275390625s
Reputation | Calculation of the PageRank for dbnary took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for dbnary took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.245208740234375e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.430511474609375e-06s
Believability | Calculation of trust value for dbnary took 7.867813110351562e-06s
INFO | --- Analysis for dbnary took 288.77605724334717s
Availability | SPARQL endpoint availability check for DBpedia took 0.5894207954406738s
Availability | VoID file availability check for DBpedia took 0.0006654262542724609s
Extra | Recovery of all triples for DBpedia took 14.681554317474365s
Performance | Total latancy measurement for DBpedia took 4.776201009750366s
Amount of data | Number of triples check for DBpedia took 3.1962649822235107s
Interoperability | New terms check for DBpedia took 10.190966844558716s
Versatility | Languages check for DBpedia took 32.062954902648926s
Interpretability | Number of blank nodes check for DBpedia took 1.0303840637207031s
Security | Check HTTPS for DBpedia took 0.15197110176086426s
Interpretability | RDF structures check for DBpedia took 10.76837682723999s
Versatility | Serialization formats check for DBpedia took 0.560894250869751s
Availability | RDF dump link check for DBpedia took 0.8567934036254883s
License | MR license check for DBpedia took 1.5877423286437988s
License | HR license check for DBpedia took 31.432645320892334s
Amount of data | Number of property check for DBpedia took 0.6654939651489258s
Understandability | Number of label check for DBpedia took 84.90020513534546s
Understandability | URI regex check for DBpedia took 2.049041748046875s
Understandability | Vocabs check for DBpedia took 5.647470235824585s
Verifiability | Authors check for DBpedia took 0.9676744937896729s
Verifiability | Publishers check for DBpedia took 0.3045780658721924s
Performance | Throughput check for DBpedia took 11.163828134536743s
Amount of data | Check the number of entities for DBpedia took 5.602836608886719e-05s
Verifiability | Contribs. check for DBpedia took 0.2933032512664795s
Interlinking | sameAs chians check for DBpedia took 3.02972674369812s
Interlinking | skos check for DBpedia took 0.8671588897705078s
Interlinking | skos check for DBpedia took 0.3390157222747803s
Timeliness | dataset update frequency check for DBpedia took 0.48706507682800293s
Currency | Creation date check for DBpedia took 0.5763964653015137s
Currency | Modification date check for DBpedia took 0.6446845531463623s
Rep.Conc. | URIs length for DBpedia took 41.691890716552734s
Interoperability | New vocabularies check for DBpedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.21059560775756836s
Accuracy | Check Functional Property for DBpedia took 0.2600545883178711s
Accuracy | Check Inverse Functional Property for DBpedia took 0.27566957473754883s
Accuracy | Check Empty annotation labels for DBpedia took 1.7636408805847168s
Accuracy | Check White space in annotation for DBpedia took 0.030774831771850586s
Accuracy | Check Datatype consistency for DBpedia took 0.02819991111755371s
Consistency | Disjoint class check for DBpedia took 0.28977370262145996s
Consistency | Check Misplaced properties for DBpedia took 31.95068860054016s
Consistency | Misplaced classes for DBpedia took 1.026698350906372s
Consistency | Check Ontology hijacking for DBpedia took 1.9819109439849854s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.1994876861572266s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.5935683250427246s
Conciseness | Check Extensional conciseness for DBpedia took 0.0322115421295166s
Conciseness | Check Intensional conciseness for DBpedia took 1.2819139957427979s
Security | Sign check for DBpedia took 0.25420618057250977s
Availability | Check URIs Dereferenciability for DBpedia took 5614.503927707672s
Completeness | Calculation of interlinking completeness for DBpedia took 1.2373683452606201s
Reputation | Calculation of the PageRank for DBpedia took 0.022230148315429688s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008974075317382812s
Interoperability | Check the re-using of existing vocabs for DBpedia took 9.5367431640625e-07s
Believability | Calculation of trust value for DBpedia took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia took 6177.08464884758s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 5.626678466796875e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0003452301025390625s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.6933331489562988s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.915496826171875e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 9.581253051757812s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.168883562088013s
Availability | VoID file availability check for DBpedia Commons took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.25261807441711426s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.961822509765625e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-commons took 16.360703945159912s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.124641418457031e-05s
Availability | VoID file availability check for DBpedia in German took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.2743077278137207s
Reputation | Calculation of the PageRank for DBpedia in German took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.985664367675781e-05s
Believability | Calculation of trust value for DBpedia in German took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-de took 3.8206727504730225s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.848556518554688s
Availability | VoID file availability check for DBpedia in Greek took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.2545022964477539s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0001971721649169922s
Believability | Calculation of trust value for DBpedia in Greek took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-el took 48.048089265823364s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.40994763374328613s
Availability | VoID file availability check for DBpedia in Spanish took 0.00072479248046875s
Extra | Recovery of all triples for DBpedia in Spanish took 22.896396160125732s
Performance | Total latancy measurement for DBpedia in Spanish took 16.30053424835205s
Amount of data | Number of triples check for DBpedia in Spanish took 4.96634578704834s
Interoperability | New terms check for DBpedia in Spanish took 15.420632362365723s
Versatility | Languages check for DBpedia in Spanish took 34.57309103012085s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.43866395950317383s
Security | Check HTTPS for DBpedia in Spanish took 0.12914037704467773s
Interpretability | RDF structures check for DBpedia in Spanish took 1.0150463581085205s
Versatility | Serialization formats check for DBpedia in Spanish took 0.6208369731903076s
Availability | RDF dump link check for DBpedia in Spanish took 4.821315050125122s
License | MR license check for DBpedia in Spanish took 4.064388990402222s
License | HR license check for DBpedia in Spanish took 33.500144243240356s
Amount of data | Number of property check for DBpedia in Spanish took 0.40410637855529785s
Understandability | Number of label check for DBpedia in Spanish took 1.6259722709655762s
Understandability | URI regex check for DBpedia in Spanish took 0.9451346397399902s
Understandability | Vocabs check for DBpedia in Spanish took 2.1374969482421875s
Verifiability | Authors check for DBpedia in Spanish took 4.063837289810181s
Verifiability | Publishers check for DBpedia in Spanish took 2.340291976928711s
Performance | Throughput check for DBpedia in Spanish took 30.77355647087097s
Amount of data | Check the number of entities for DBpedia in Spanish took 3.3855438232421875e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 3.3208961486816406s
Interlinking | sameAs chians check for DBpedia in Spanish took 2.7541186809539795s
Interlinking | skos check for DBpedia in Spanish took 3.486673593521118s
Interlinking | skos check for DBpedia in Spanish took 2.8545031547546387s
Timeliness | dataset update frequency check for DBpedia in Spanish took 3.9809744358062744s
Currency | Creation date check for DBpedia in Spanish took 8.08139157295227s
Currency | Modification date check for DBpedia in Spanish took 5.310833692550659s
Rep.Conc. | URIs length for DBpedia in Spanish took 32.47893738746643s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 3.7364299297332764s
Accuracy | Check Functional Property for DBpedia in Spanish took 3.4308395385742188s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 3.3457834720611572s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 14.48415493965149s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.030773162841796875s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.02713155746459961s
Consistency | Disjoint class check for DBpedia in Spanish took 2.777770519256592s
Consistency | Check Misplaced properties for DBpedia in Spanish took 23.174561738967896s
Consistency | Misplaced classes for DBpedia in Spanish took 12.530451536178589s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 14.331617593765259s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.1745505332946777s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 14.555038690567017s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03419899940490723s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 13.419023275375366s
Security | Sign check for DBpedia in Spanish took 2.7531578540802s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 22.49885630607605s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.7169802188873291s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021044492721557617s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011229515075683594s
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 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-es took 942.6589465141296s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.1119625568389893s
Availability | VoID file availability check for DBpedia in Basque took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.297102689743042s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.2901763916015625e-05s
Believability | Calculation of trust value for DBpedia in Basque took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-eu took 9.37256669998169s
Availability | SPARQL endpoint availability check for DBpedia in French took 47.688281774520874s
Availability | VoID file availability check for DBpedia in French took 0.0004210472106933594s
Extra | Recovery of all triples for DBpedia in French took 233.48422980308533s
Amount of data | Number of triples check for DBpedia in French took 10.002803802490234s
Interoperability | New terms check for DBpedia in French took 57.80242156982422s
Versatility | Languages check for DBpedia in French took 300.09872674942017s
Interpretability | Number of blank nodes check for DBpedia in French took 33.38556170463562s
Interpretability | RDF structures check for DBpedia in French took 29.403811931610107s
Versatility | Serialization formats check for DBpedia in French took 125.80761003494263s
Availability | RDF dump link check for DBpedia in French took 3503.019514322281s
License | MR license check for DBpedia in French took 10.174997329711914s
License | HR license check for DBpedia in French took 10.000957489013672s
Amount of data | Number of property check for DBpedia in French took 9.996329545974731s
Understandability | Number of label check for DBpedia in French took 57.997313022613525s
Understandability | URI regex check for DBpedia in French took 65.88606762886047s
Understandability | Vocabs check for DBpedia in French took 45.806076526641846s
Verifiability | Authors check for DBpedia in French took 10.012710332870483s
Verifiability | Publishers check for DBpedia in French took 10.005272388458252s
Amount of data | Check the number of entities for DBpedia in French took 9.489059448242188e-05s
Verifiability | Contribs. check for DBpedia in French took 9.997763872146606s
Interlinking | sameAs chians check for DBpedia in French took 56.396892786026s
Interlinking | skos check for DBpedia in French took 43.00855493545532s
Interlinking | skos check for DBpedia in French took 10.100637197494507s
Timeliness | dataset update frequency check for DBpedia in French took 50.07601308822632s
Currency | Creation date check for DBpedia in French took 20.021339178085327s
Currency | Modification date check for DBpedia in French took 200.25499486923218s
Rep.Conc. | URIs length for DBpedia in French took 26.000718355178833s
Interoperability | New vocabularies check for DBpedia in French took 114.08373618125916s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 78.92265319824219s
Accuracy | Check Empty annotation labels for DBpedia in French took 92.74683880805969s
Accuracy | Check White space in annotation for DBpedia in French took 3.075049638748169s
Accuracy | Check Datatype consistency for DBpedia in French took 2.61844801902771s
Consistency | Disjoint class check for DBpedia in French took 10.063728332519531s
Consistency | Check Ontology hijacking for DBpedia in French took 10.104697465896606s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 11.218000411987305s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.014301300048828s
Security | Sign check for DBpedia in French took 55.039673805236816s
Availability | Check URIs Dereferenciability for DBpedia in French took 4713.255796909332s
Completeness | Calculation of interlinking completeness for DBpedia in French took 1.6090216636657715s
Reputation | Calculation of the PageRank for DBpedia in French took 0.02209019660949707s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 5.9604644775390625e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00010204315185546875s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 71.24453926086426s
Believability | Calculation of trust value for DBpedia in French took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-fr took 11752.208491563797s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9622299671173096s
Availability | VoID file availability check for DBpedia in Japanese took 4.047125339508057s
Extra | Recovery of all triples for DBpedia in Japanese took 8.677815437316895s
Performance | Total latancy measurement for DBpedia in Japanese took 6.65856146812439s
Amount of data | Number of triples check for DBpedia in Japanese took 121.32280540466309s
Interoperability | New terms check for DBpedia in Japanese took 20.857871294021606s
Versatility | Languages check for DBpedia in Japanese took 1.7538809776306152s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3516159057617188s
Security | Check HTTPS for DBpedia in Japanese took 0.7999053001403809s
Interpretability | RDF structures check for DBpedia in Japanese took 1.6984097957611084s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3420405387878418s
Availability | RDF dump link check for DBpedia in Japanese took 1.3320996761322021s
License | MR license check for DBpedia in Japanese took 1.9234046936035156s
License | HR license check for DBpedia in Japanese took 121.3390519618988s
Amount of data | Number of property check for DBpedia in Japanese took 1.3766288757324219s
Understandability | Number of label check for DBpedia in Japanese took 9.276288032531738s
Understandability | URI regex check for DBpedia in Japanese took 2.668607234954834s
Understandability | Vocabs check for DBpedia in Japanese took 1.4401788711547852s
Verifiability | Authors check for DBpedia in Japanese took 1.3381011486053467s
Verifiability | Publishers check for DBpedia in Japanese took 1.3914551734924316s
Performance | Throughput check for DBpedia in Japanese took 13.251278162002563s
Amount of data | Check the number of entities for DBpedia in Japanese took 8.058547973632812e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.329005241394043s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.783827781677246s
Interlinking | skos check for DBpedia in Japanese took 2.0451273918151855s
Interlinking | skos check for DBpedia in Japanese took 1.7389168739318848s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3484277725219727s
Currency | Creation date check for DBpedia in Japanese took 2.826077699661255s
Currency | Modification date check for DBpedia in Japanese took 2.6961653232574463s
Rep.Conc. | URIs length for DBpedia in Japanese took 139.89696097373962s
Interoperability | New vocabularies check for DBpedia in Japanese took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3371927738189697s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.444695472717285s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.025831937789916992s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.029529809951782227s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4713184833526611s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.65323424339294s
Consistency | Misplaced classes for DBpedia in Japanese took 3.8410801887512207s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.789293050765991s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.1912760734558105s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.5001904964447s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03468179702758789s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 4.991504669189453s
Security | Sign check for DBpedia in Japanese took 1.3600695133209229s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 9.911937952041626s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 1.343047857284546s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02168440818786621s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00011992454528808594s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-ja took 1349.1985552310944s
Availability | SPARQL endpoint availability check for dbpedia lite took 5.602836608886719e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.37247180938720703s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020841360092163086s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010323524475097656s
Believability | Calculation of trust value for dbpedia lite took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-lite took 23.77701187133789s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.00543212890625e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.27344775199890137s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 2.956390380859375e-05s
Believability | Calculation of trust value for DBpedia-Live took 6.67572021484375e-06s
INFO | --- Analysis for dbpedia-live took 5.069368600845337s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.28404712677001953s
Availability | VoID file availability check for DBpedia in Dutch took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.23812556266784668s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00018095970153808594s
Believability | Calculation of trust value for DBpedia in Dutch took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-nl took 3.1149232387542725s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 30.18433690071106s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.2581801414489746s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.368492126464844e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-pt took 74.0832872390747s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.0531158447265625e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0003933906555175781s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.26067566871643066s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 2.8848648071289062e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-spotlight took 3.9125072956085205s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.315376281738281e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2488112449645996s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.604194641113281e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.050971508026123s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.029273986816406e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.24637818336486816s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.0279159545898438e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.2405996322631836s
Availability | SPARQL endpoint availability check for DBpedia took 4.1484832763671875e-05s
Availability | VoID file availability check for DBpedia took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for DBpedia took 0.2366492748260498s
Reputation | Calculation of the PageRank for DBpedia took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.8371810913085938e-05s
Believability | Calculation of trust value for DBpedia took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia_ took 3.5992825031280518s
Availability | SPARQL endpoint availability check for DBTropes took 4.2438507080078125e-05s
Availability | VoID file availability check for DBTropes took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for DBTropes took 0.24567627906799316s
Reputation | Calculation of the PageRank for DBTropes took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.369850158691406e-05s
Believability | Calculation of trust value for DBTropes took 6.9141387939453125e-06s
INFO | --- Analysis for dbtropes took 3.182065486907959s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.220008850097656e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.23918414115905762s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 7.867813110351562e-06s
INFO | --- Analysis for dbtune took 3.2830259799957275s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.315376281738281e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0003559589385986328s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.24828076362609863s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.626678466796875e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.53935432434082s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.220008850097656e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.00034999847412109375s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.25568127632141113s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.337860107421875e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.879712104797363s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.990330934524536s
Availability | VoID file availability check for DBTune.org/classical took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.27875375747680664s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020876169204711914s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.987022399902344e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-classical took 22.54949641227722s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.37796139717102s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0008177757263183594s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2552299499511719s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.581710815429688e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 8.106231689453125e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 26.90356993675232s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 7.913920640945435s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0008265972137451172s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2875792980194092s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.021009206771850586s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.000997304916381836s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 8.535385131835938e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-magnatune took 23.896807432174683s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.377063274383545s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.26839256286621094s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011181831359863281s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.91247010231018s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.376312732696533s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2762417793273926s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.5789947509765625e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 8.58306884765625e-06s
INFO | --- Analysis for dbtune-myspace took 17.907779932022095s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.076957702636719e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.25397801399230957s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.0040740966796875e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.62939453125e-06s
INFO | --- Analysis for dclg-openuplabs took 2.8942105770111084s
Availability | SPARQL endpoint availability check for data.dcs took 4.220008850097656e-05s
Availability | VoID file availability check for data.dcs took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for data.dcs took 0.2598273754119873s
Reputation | Calculation of the PageRank for data.dcs took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.842613220214844e-05s
Believability | Calculation of trust value for data.dcs took 7.3909759521484375e-06s
INFO | --- Analysis for dcs-sheffield took 2.4612231254577637s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 8.177757263183594e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.23951268196105957s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.4332275390625e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 1.0251998901367188e-05s
INFO | --- Analysis for de-budget took 2.8374624252319336s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.363059997558594e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.28388333320617676s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.7670135498046875e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.867813110351562e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.193749904632568s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.458427429199219e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.25601625442504883s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.696846008300781e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 8.106231689453125e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.5591089725494385s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.3392181396484375e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.26375365257263184s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.0994415283203125e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.152557373046875e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.9368364810943604s
Availability | SPARQL endpoint availability check for Demografie took 4.649162292480469e-05s
Availability | VoID file availability check for Demografie took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Demografie took 0.2577188014984131s
Reputation | Calculation of the PageRank for Demografie took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.9325485229492188e-05s
Believability | Calculation of trust value for Demografie took 1.1205673217773438e-05s
INFO | --- Analysis for demografie took 2.8540053367614746s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.315376281738281e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.3070254325866699s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.528594970703125e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.239776611328125e-05s
INFO | --- Analysis for desaparecidos took 2.751596212387085s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.291534423828125e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.25598692893981934s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020433664321899414s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010132789611816406s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 8.106231689453125e-06s
INFO | --- Analysis for deustoentrepreneurship took 4.186662912368774s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.2438507080078125e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2792694568634033s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.021654844284057617s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00012063980102539062s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 7.3909759521484375e-06s
INFO | --- Analysis for deustotech took 4.369723320007324s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.475771427154541s
Availability | VoID file availability check for Deutsche Biographie took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.24599051475524902s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.981590270996094e-05s
Believability | Calculation of trust value for Deutsche Biographie took 8.344650268554688e-06s
INFO | --- Analysis for deutsche-biographie took 4.2696309089660645s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 7.915496826171875e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2693452835083008s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.02086043357849121s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0010192394256591797s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 6.556510925292969e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.867813110351562e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.699672222137451s
Availability | SPARQL endpoint availability check for dev8d took 4.1961669921875e-05s
Availability | VoID file availability check for dev8d took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for dev8d took 0.2662184238433838s
Reputation | Calculation of the PageRank for dev8d took 0.021369457244873047s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.890296936035156e-05s
Believability | Calculation of trust value for dev8d took 8.58306884765625e-06s
INFO | --- Analysis for dev8d took 2.754410982131958s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.21665382385254s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007739067077636719s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.6907029151916504s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.507469177246094e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 7.62939453125e-06s
INFO | --- Analysis for dewey_decimal_classification took 93.34331488609314s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.291534423828125e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.25416016578674316s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.6716461181640625e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 6.9141387939453125e-06s
INFO | --- Analysis for DHSVM took 23.419870138168335s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.1484832763671875e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.258192777633667s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 2.9325485229492188e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 7.62939453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.868410110473633s
Availability | SPARQL endpoint availability check for Diavgeia took 4.458427429199219e-05s
Availability | VoID file availability check for Diavgeia took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.27825427055358887s
Reputation | Calculation of the PageRank for Diavgeia took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.678436279296875e-05s
Believability | Calculation of trust value for Diavgeia took 5.245208740234375e-06s
INFO | --- Analysis for diavgeia took 5.695707321166992s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.291534423828125e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.2770285606384277s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011730194091796875s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for didactalia took 342.0804522037506s
Availability | SPARQL endpoint availability check for diigo.feed took 4.482269287109375e-05s
Availability | VoID file availability check for diigo.feed took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.23839378356933594s
Reputation | Calculation of the PageRank for diigo.feed took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.9325485229492188e-05s
Believability | Calculation of trust value for diigo.feed took 7.152557373046875e-06s
INFO | --- Analysis for diigo-feed took 4.726386785507202s
Availability | SPARQL endpoint availability check for DisGeNET took 0.9125473499298096s
Availability | VoID file availability check for DisGeNET took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2577807903289795s
Reputation | Calculation of the PageRank for DisGeNET took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015211105346679688s
Believability | Calculation of trust value for DisGeNET took 7.152557373046875e-06s
INFO | --- Analysis for disgenet took 8.405166864395142s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.27772045135498047s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.956390380859375e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for disk took 3.7663471698760986s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.1484832763671875e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.25579237937927246s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 2.956390380859375e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 6.9141387939453125e-06s
INFO | --- Analysis for distritos-zaragoza took 2.912569284439087s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 6.937980651855469e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2512087821960449s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.075599670410156e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 6.9141387939453125e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 8.912283420562744s
Availability | SPARQL endpoint availability check for DM2E took 4.2438507080078125e-05s
Availability | VoID file availability check for DM2E took 0.00037026405334472656s
Completeness | Calculation of interlinking completeness for DM2E took 0.2453606128692627s
Reputation | Calculation of the PageRank for DM2E took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for DM2E took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0009660720825195312s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.0001220703125s
Believability | Calculation of trust value for DM2E took 7.62939453125e-06s
INFO | --- Analysis for dm2e took 3.3827414512634277s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.00543212890625e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.2476794719696045s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.0202176570892334s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 2.8848648071289062e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.867813110351562e-06s
INFO | --- Analysis for dmoz_rdf_dump took 3.253570556640625s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.7331037521362305s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.30712175369262695s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001552104949951172s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 7.867813110351562e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 11.046374082565308s
Availability | SPARQL endpoint availability check for DOAP Store took 4.100799560546875e-05s
Availability | VoID file availability check for DOAP Store took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.26876044273376465s
Reputation | Calculation of the PageRank for DOAP Store took 0.03099513053894043s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0014569759368896484s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 4.673004150390625e-05s
Believability | Calculation of trust value for DOAP Store took 7.62939453125e-06s
INFO | --- Analysis for doap_store took 3.0066871643066406s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.315376281738281e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0007715225219726562s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.2525300979614258s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.02093338966369629s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.222724914550781e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.4836273193359375e-06s
INFO | --- Analysis for doi took 10.008178949356079s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.2438507080078125e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.2848236560821533s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.02054905891418457s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.9325485229492188e-05s
Believability | Calculation of trust value for Driggu Florentino took 7.867813110351562e-06s
INFO | --- Analysis for Driggu took 3.554556131362915s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.899040460586548s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.2706930637359619s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.814697265625e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 7.152557373046875e-06s
INFO | --- Analysis for drug-data-hifm took 38.50214076042175s
Availability | SPARQL endpoint availability check for dspace took 6.341934204101562e-05s
Availability | VoID file availability check for dspace took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for dspace took 0.25675129890441895s
Reputation | Calculation of the PageRank for dspace took 0.020963191986083984s
Interlinking | Calculation of Degree of Connection for dspace took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for dspace took 0.0009737014770507812s
Interlinking | Calculation of Clustering coefficient for dspace took 3.4809112548828125e-05s
Believability | Calculation of trust value for dspace took 8.106231689453125e-06s
INFO | --- Analysis for dspace took 2.8038346767425537s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 5.7697296142578125e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2590217590332031s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.0213162899017334s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0009760856628417969s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.504753112792969e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 7.867813110351562e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.9199090003967285s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.08405113220215s
Availability | VoID file availability check for MetaLex Document Server took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.3316042423248291s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02100515365600586s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.9577484130859375e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.867813110351562e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 554.4003057479858s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.7481889724731445s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.6762745380401611s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020610570907592773s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.886222839355469e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.152557373046875e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 12.43372130393982s
Availability | SPARQL endpoint availability check for DWS-Group took 4.3392181396484375e-05s
Availability | VoID file availability check for DWS-Group took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2701089382171631s
Reputation | Calculation of the PageRank for DWS-Group took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00011014938354492188s
Believability | Calculation of trust value for DWS-Group took 7.152557373046875e-06s
INFO | --- Analysis for dws-group took 3.449045181274414s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.3392181396484375e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.3565988540649414s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.9087066650390625e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 7.152557373046875e-06s
INFO | --- Analysis for E1 took 5.07231330871582s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.06391000747680664s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.25461697578430176s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02057027816772461s
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.000732421875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011086463928222656s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-alaska took 2.3981142044067383s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.03859591484069824s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0003521442413330078s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.27890706062316895s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.3882598876953125e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-cau took 2.4750843048095703s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.04581928253173828s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2686941623687744s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02633523941040039s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0013935565948486328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 9.965896606445312e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.491936683654785s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.03465104103088379s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2636990547180176s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.369850158691406e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.3734757900238037s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.03896689414978027s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.25205564498901367s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013709068298339844s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.430494546890259s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04158520698547363s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2614326477050781s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.845329284667969e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-famu took 2.465266704559326s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04183340072631836s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.26699090003967285s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.021216630935668945s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013065338134765625s
Believability | Calculation of trust value for eagle-i @ Harvard University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-harvard took 2.3744311332702637s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.06591916084289551s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2597634792327881s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001316070556640625s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.434141159057617s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.06566476821899414s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2696869373321533s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.890296936035156e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-howard took 2.54191517829895s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.04262065887451172s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.26941967010498047s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020893573760986328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.000988006591796875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.82012939453125e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.476926326751709s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.03978729248046875s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.26468539237976074s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011515617370605469s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-jsu took 2.906695604324341s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.04533839225769043s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00036978721618652344s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.27033376693725586s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.719329833984375e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-meharry took 2.4950919151306152s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04055619239807129s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2785344123840332s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010728836059570312s
Believability | Calculation of trust value for eagle-i @ Montana State University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-montana took 2.4414501190185547s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.0391232967376709s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.257159948348999s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.608268737792969e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-msm took 2.3776206970214844s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.042917490005493164s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.26641011238098145s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.021486520767211914s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00014901161193847656s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.465474843978882s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.03877615928649902s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00034117698669433594s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.26645612716674805s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-psm took 2.399178981781006s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.03977537155151367s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.2754542827606201s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.914138793945312e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-tsu took 2.440748929977417s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.04580879211425781s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00037598609924316406s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2681140899658203s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.318092346191406e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.4511919021606445s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.04594612121582031s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00036406517028808594s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.25768208503723145s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.703636169433594e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.547058343887329s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04487299919128418s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2677123546600342s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012683868408203125s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-upr took 2.4173073768615723s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.03146982192993164s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2519657611846924s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.246566772460938e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-utep took 2.403541088104248s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.03945565223693848s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.26427292823791504s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.937980651855469e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-utsa took 2.479351282119751s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.14403915405273438s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.2634401321411133s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 0.00010991096496582031s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.5308620929718018s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.04620218276977539s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.25009751319885254s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.462501525878906e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-xula took 2.517073154449463s
Availability | SPARQL endpoint availability check for Emergency situation took 0.7821977138519287s
Availability | VoID file availability check for Emergency situation took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.27566981315612793s
Reputation | Calculation of the PageRank for Emergency situation took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.887580871582031e-05s
Believability | Calculation of trust value for Emergency situation took 7.62939453125e-06s
INFO | --- Analysis for Earthquake took 3.8535733222961426s
Availability | SPARQL endpoint availability check for ESO took 0.6556103229522705s
Availability | VoID file availability check for ESO took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for ESO took 0.2709665298461914s
Reputation | Calculation of the PageRank for ESO took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for ESO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for ESO took 8.130073547363281e-05s
Believability | Calculation of trust value for ESO took 7.62939453125e-06s
INFO | --- Analysis for Earthquake_case took 4.208947658538818s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.2510840892791748s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.25306010246276855s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010132789611816406s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for ecb-linked-data took 2.6895253658294678s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.236629962921143s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0007712841033935547s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.24988269805908203s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.0205385684967041s
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.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.719329833984375e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.0067901611328125e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 10.274458646774292s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.7983908653259277s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2816503047943115s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.022225618362426758s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 7.43865966796875e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 5.991602659225464s
Availability | SPARQL endpoint availability check for ECLAP took 20.653385877609253s
Availability | VoID file availability check for ECLAP took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for ECLAP took 0.26746606826782227s
Reputation | Calculation of the PageRank for ECLAP took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.9577484130859375e-05s
Believability | Calculation of trust value for ECLAP took 7.3909759521484375e-06s
INFO | --- Analysis for eclap took 53.08942270278931s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.4345855712890625e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.3092012405395508s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.0211031436920166s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.2159347534179688e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 5.7220458984375e-06s
INFO | --- Analysis for ECNU-GISer took 183.8411464691162s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.172325134277344e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2472686767578125s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02100372314453125s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.745887756347656e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 6.67572021484375e-06s
INFO | --- Analysis for ecs took 2.3535680770874023s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.076957702636719e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.2901740074157715s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.123283386230469e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 6.198883056640625e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.910301923751831s
Availability | SPARQL endpoint availability check for Edublogs took 4.029273986816406e-05s
Availability | VoID file availability check for Edublogs took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Edublogs took 0.26061034202575684s
Reputation | Calculation of the PageRank for Edublogs took 0.02085089683532715s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010013580322265625s
Believability | Calculation of trust value for Edublogs took 6.4373016357421875e-06s
INFO | --- Analysis for edublogs took 3.2590341567993164s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.6715497970581055s
Availability | VoID file availability check for education.data.gov.uk took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.27486228942871094s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.036064147949219e-05s
Believability | Calculation of trust value for education.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for education-data-gov-uk took 4.857285737991333s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 3.933906555175781e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2503228187561035s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020998716354370117s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.266334533691406e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.152557373046875e-06s
INFO | --- Analysis for education-openuplabs took 2.9340059757232666s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.07330894470215s
Availability | VoID file availability check for Educational programs - SISVU took 0.0009915828704833984s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.8425438404083252s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02147650718688965s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 4.76837158203125e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.62939453125e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1323.3851110935211s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.8036351203918457s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2527039051055908s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02218484878540039s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0009868144989013672s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 5.030632019042969e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.4836273193359375e-06s
INFO | --- Analysis for eea took 8.434598922729492s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5789899826049805s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.28760695457458496s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.173683166503906e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.245208740234375e-06s
INFO | --- Analysis for eea-rod took 6.478518724441528s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.18043804168701172s
Availability | VoID file availability check for EEA Vocabularies took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.29497647285461426s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.606910705566406e-05s
Believability | Calculation of trust value for EEA Vocabularies took 7.62939453125e-06s
INFO | --- Analysis for eea-vocabularies took 5.231925010681152s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 5.1975250244140625e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.25377845764160156s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for ege-university-linked-open-data took 3.390507459640503s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.4609646797180176s
Availability | VoID file availability check for E-Government Ontology took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2926912307739258s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for E-Government Ontology took 8.58306884765625e-06s
INFO | --- Analysis for EGovOntology took 3.5388741493225098s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.572218656539917s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006153583526611328s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.1521220207214355s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3058018684387207s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8715715408325195s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8388829231262207s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.34796690940857s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.83874249458313s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.807358980178833s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1139938831329346s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.297452449798584s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6006836891174316s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 7.1278157234191895s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26157379150390625s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5364155769348145s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6637327671051025s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3343234062194824s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3938155174255371s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2621731758117676s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.77344799041748s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.176399230957031e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40073108673095703s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.31554722785949707s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.622927188873291s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3971240520477295s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.144993543624878s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.2368083000183105s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5067582130432129s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.965311050415039s
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.2415773868560791s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.39385008811950684s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.32662296295166016s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.324366569519043s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030145883560180664s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.028772830963134766s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2763075828552246s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.405511140823364s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5599892139434814s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.5793004035949707s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2056944370269775s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.556467771530151s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.035996198654174805s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.43283772468566895s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.526240348815918s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3208.7928948402405s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1352593898773193s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0216062068939209s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 6.628036499023438e-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.3909759521484375e-06s
INFO | --- Analysis for ei2a took 13789.322083473206s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 7.843971252441406e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.7324018478393555s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.000110626220703125s
Believability | Calculation of trust value for EIONET RDF Data took 1.1205673217773438e-05s
INFO | --- Analysis for eionet-rdf took 3.957333564758301s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.458427429199219e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.2528088092803955s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.021123886108398438s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.24249267578125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 7.152557373046875e-06s
INFO | --- Analysis for ElgooG_ took 2.803391456604004s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.482269287109375e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2665696144104004s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.02087545394897461s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.1948089599609375e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.867813110351562e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 3.7240045070648193s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.23844861984253s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.25690340995788574s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.486343383789062e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 8.106231689453125e-06s
INFO | --- Analysis for elviajero took 27.95408606529236s
Availability | SPARQL endpoint availability check for EMN took 4.3392181396484375e-05s
Availability | VoID file availability check for EMN took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for EMN took 0.26964235305786133s
Reputation | Calculation of the PageRank for EMN took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for EMN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for EMN took 4.100799560546875e-05s
Believability | Calculation of trust value for EMN took 7.152557373046875e-06s
INFO | --- Analysis for emn took 2.6836953163146973s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.25733017921447754s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.459785461425781e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 2.3126602172851562e-05s
INFO | --- Analysis for enakting-co2emission took 2.4011223316192627s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.25760722160339355s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.3392181396484375e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-crime took 2.3702454566955566s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.410743713378906e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.26410603523254395s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.124641418457031e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-energy took 2.3841071128845215s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.5299530029296875e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.2529613971710205s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.226799011230469e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-mortality took 2.3316636085510254s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2794458866119385s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.021147966384887695s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 9.5367431640625e-06s
INFO | --- Analysis for enakting-nhs took 2.4287502765655518s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 8.797645568847656e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00042724609375s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2652256488800049s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02084660530090332s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.602836608886719e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-population took 2.3857362270355225s
Availability | SPARQL endpoint availability check for Enel Shops took 3.910064697265625e-05s
Availability | VoID file availability check for Enel Shops took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2634124755859375s
Reputation | Calculation of the PageRank for Enel Shops took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.123283386230469e-05s
Believability | Calculation of trust value for Enel Shops took 7.152557373046875e-06s
INFO | --- Analysis for enel-shops took 2.797106981277466s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.0531158447265625e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.2794523239135742s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.0517578125e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 6.67572021484375e-06s
INFO | --- Analysis for energy-efficiency took 2.884795665740967s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.2888960838317871s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.918907403945923s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 8.058547973632812e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2548370361328125s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.24249267578125e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.8734402656555176s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.27989745140075684s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.900197744369507s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.25981807708740234s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.528594970703125e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.8695759773254395s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.2422008514404297s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.24249267578125e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.795173168182373s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.2638258934020996s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020959138870239258s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0010592937469482422s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 4.100799560546875e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.8733465671539307s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.26535534858703613s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.8529176712036133s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 1.0087246894836426s
Availability | VoID file availability check for English Heritage Periods List took 0.0007631778717041016s
Extra | Recovery of all triples for English Heritage Periods List took 0.4403727054595947s
Performance | Total latancy measurement for English Heritage Periods List took 2.043948173522949s
Amount of data | Number of triples check for English Heritage Periods List took 0.6145203113555908s
Versatility | Languages check for English Heritage Periods List took 0.3663778305053711s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.593113899230957s
Security | Check HTTPS for English Heritage Periods List took 0.2598886489868164s
Interpretability | RDF structures check for English Heritage Periods List took 0.35325002670288086s
Versatility | Serialization formats check for English Heritage Periods List took 0.6293215751647949s
Availability | RDF dump link check for English Heritage Periods List took 0.4008011817932129s
License | MR license check for English Heritage Periods List took 0.48670363426208496s
License | HR license check for English Heritage Periods List took 0.4640223979949951s
Amount of data | Number of property check for English Heritage Periods List took 0.5065829753875732s
Understandability | Number of label check for English Heritage Periods List took 0.6077754497528076s
Understandability | URI regex check for English Heritage Periods List took 0.8092000484466553s
Understandability | Vocabs check for English Heritage Periods List took 0.4960181713104248s
Verifiability | Authors check for English Heritage Periods List took 0.48034191131591797s
Verifiability | Publishers check for English Heritage Periods List took 0.42816662788391113s
Performance | Throughput check for English Heritage Periods List took 12.364132404327393s
Amount of data | Check the number of entities for English Heritage Periods List took 7.2479248046875e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.41900634765625s
Interlinking | sameAs chians check for English Heritage Periods List took 0.40493154525756836s
Interlinking | skos check for English Heritage Periods List took 0.41150498390197754s
Interlinking | skos check for English Heritage Periods List took 0.40802812576293945s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.49780917167663574s
Currency | Creation date check for English Heritage Periods List took 0.7890110015869141s
Currency | Modification date check for English Heritage Periods List took 0.8687019348144531s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8457872867584229s
Interoperability | New vocabularies check for English Heritage Periods List took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.41779661178588867s
Accuracy | Check Functional Property for English Heritage Periods List took 0.4211728572845459s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.38494277000427246s
Consistency | Disjoint class check for English Heritage Periods List took 0.4138205051422119s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.5385997295379639s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6736822128295898s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00013971328735351562s
Security | Sign check for English Heritage Periods List took 0.4624819755554199s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.2473158836364746s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.52587890625e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-periods-list took 61.39589023590088s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.3860433101654053s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0011200904846191406s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.265606164932251s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020684003829956055s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.409385681152344e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 9.5367431640625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 3.816804885864258s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.23949098587036133s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.2565467357635498s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.337860107421875e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.7220458984375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 3.742955446243286s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.029273986816406e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.24507951736450195s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020425081253051758s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.147125244140625e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 7.62939453125e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.879911184310913s
Availability | SPARQL endpoint availability check for English WordNet took 5.2928924560546875e-05s
Availability | VoID file availability check for English WordNet took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for English WordNet took 0.2636122703552246s
Reputation | Calculation of the PageRank for English WordNet took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.314018249511719e-05s
Believability | Calculation of trust value for English WordNet took 7.3909759521484375e-06s
INFO | --- Analysis for english-wordnet took 3.286850929260254s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.24502205848693848s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.123283386230469e-05s
Believability | Calculation of trust value for English Heritage Places took 6.67572021484375e-06s
INFO | --- Analysis for englishheritage_places took 2.813889503479004s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.1343395709991455s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.29248595237731934s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 0.00010919570922851562s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 8.106231689453125e-06s
INFO | --- Analysis for enipedia took 2.6266753673553467s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.291534423828125e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.25917863845825195s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.075599670410156e-05s
Believability | Calculation of trust value for Enslaved.org took 7.867813110351562e-06s
INFO | --- Analysis for enslaved.org took 4.886341571807861s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.05157804489135742s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.25259852409362793s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.245208740234375e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for entice-graph took 2.4536795616149902s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.363059997558594e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008106231689453125s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2685415744781494s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02081584930419922s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.5762786865234375e-05s
Believability | Calculation of trust value for Entrez Gene took 6.9141387939453125e-06s
INFO | --- Analysis for entrez_gene took 30.037271976470947s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.124641418457031e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.2578420639038086s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.075599670410156e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.152557373046875e-06s
INFO | --- Analysis for entrez_gene_extract took 2.7844901084899902s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0760273933410645s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0007419586181640625s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.2446882724761963s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.021187782287597656s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.1021575927734375e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 5.7220458984375e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 11.896407842636108s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.31673574447631836s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2608661651611328s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.6253204345703125e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.670920610427856s
Availability | SPARQL endpoint availability check for EARTh took 270.7495572566986s
Availability | VoID file availability check for EARTh took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for EARTh took 0.27925944328308105s
Reputation | Calculation of the PageRank for EARTh took 0.020898103713989258s
Interlinking | Calculation of Degree of Connection for EARTh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.417533874511719e-05s
Believability | Calculation of trust value for EARTh took 6.9141387939453125e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 562.2754428386688s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.6136474609375s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.00026798248291015625s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 118.33114171028137s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 1.0021533966064453s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 8.026034116744995s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 13.778832912445068s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.18019676208496s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.820357084274292s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.27454161643981934s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 9.63927960395813s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.2690098285675049s
License | MR license check for Micka (EO metadata) @PSNC took 0.5531530380249023s
License | HR license check for Micka (EO metadata) @PSNC took 300.1963291168213s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.32037925720214844s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.5012943744659424s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.8824036121368408s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.4450416564941406s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.2044215202331543s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.2753286361694336s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.639952898025513s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 7.271766662597656e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.1846921443939209s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.1999199390411377s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4499478340148926s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.43392443656921387s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 7.24651575088501s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.491793155670166s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.2284228801727295s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 151.0951054096222s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.19876480102539062s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.3607065677642822s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.34214329719543457s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 40.85861396789551s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.690825939178467s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.7904891967773438s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.19485139846801758s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 82.91056060791016s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.421448230743408s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 34.68161916732788s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.2477850914001465s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 81.80691242218018s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.7313313484191895s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5547988414764404s
Security | Sign check for Micka (EO metadata) @PSNC took 0.519934892654419s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 9.765334606170654s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 1.3608031272888184s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021569252014160156s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for EO_metadata took 2259.558002471924s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.601478576660156e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.26712656021118164s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020988941192626953s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.0517578125e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 6.9141387939453125e-06s
INFO | --- Analysis for EOKP-Datasets took 4.868352890014648s
Availability | SPARQL endpoint availability check for EPA-CDR took 0.00013780593872070312s
Availability | VoID file availability check for EPA-CDR took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.26718735694885254s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.504753112792969e-05s
Believability | Calculation of trust value for EPA-CDR took 5.9604644775390625e-06s
INFO | --- Analysis for epa-cdr took 8.59438705444336s
Availability | SPARQL endpoint availability check for EPA-FRS took 6.842613220214844e-05s
Availability | VoID file availability check for EPA-FRS took 0.001215219497680664s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2888627052307129s
Reputation | Calculation of the PageRank for EPA-FRS took 0.021000385284423828s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.271766662597656e-05s
Believability | Calculation of trust value for EPA-FRS took 5.245208740234375e-06s
INFO | --- Analysis for epa-frs took 6.0954039096832275s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.1961669921875e-05s
Availability | VoID file availability check for EPA-RCRA took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.26631808280944824s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0008609294891357422s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.719329833984375e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.0067901611328125e-06s
INFO | --- Analysis for epa-rcra took 5.689720869064331s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.2438507080078125e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.2924520969390869s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.772445678710938e-05s
Believability | Calculation of trust value for EPA-SRS took 5.9604644775390625e-06s
INFO | --- Analysis for epa-srs took 5.746306419372559s
Availability | SPARQL endpoint availability check for EPA-TRI took 5.221366882324219e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2678654193878174s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.361701965332031e-05s
Believability | Calculation of trust value for EPA-TRI took 5.0067901611328125e-06s
INFO | --- Analysis for epa-tri took 5.740804433822632s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.100799560546875e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.2638356685638428s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.915496826171875e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 8.344650268554688e-06s
INFO | --- Analysis for epo took 2.8870418071746826s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.04114532470703125s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.27748799324035645s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0008170604705810547s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013780593872070312s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.4430859088897705s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5958702564239502s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.2599618434906006s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.344650268554688e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 7.3909759521484375e-06s
INFO | --- Analysis for eprtr took 3.7446327209472656s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 1.0496020317077637s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.24682044982910156s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.021085262298583984s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.0994415283203125e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 7.152557373046875e-06s
INFO | --- Analysis for ERAKG took 3.465679168701172s
Availability | SPARQL endpoint availability check for reg took 4.267692565917969e-05s
Availability | VoID file availability check for reg took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for reg took 0.27391695976257324s
Reputation | Calculation of the PageRank for reg took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for reg took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for reg took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for reg took 1.1920928955078125e-05s
Believability | Calculation of trust value for reg took 7.3909759521484375e-06s
INFO | --- Analysis for erg took 2.344000816345215s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.23569202423095703s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.25606632232666016s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.0994415283203125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.9604644775390625e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.814283847808838s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 5.2928924560546875e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.27571916580200195s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0008473396301269531s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.822845458984375e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.0067901611328125e-06s
INFO | --- Analysis for esd-standards took 4.094647645950317s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.2438507080078125e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.27875709533691406s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020661115646362305s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.271766662597656e-05s
Believability | Calculation of trust value for ESD-Toolkit took 5.245208740234375e-06s
INFO | --- Analysis for esd-toolkit took 3.3240420818328857s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.291534423828125e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.23990583419799805s
Reputation | Calculation of the PageRank for Dataset Esis took 0.022104263305664062s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0008413791656494141s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.552436828613281e-05s
Believability | Calculation of trust value for Dataset Esis took 7.152557373046875e-06s
INFO | --- Analysis for esislearning took 3.2938144207000732s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.482269287109375e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0003592967987060547s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.25499701499938965s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.0279159545898438e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 7.152557373046875e-06s
INFO | --- Analysis for ESV took 23.871840000152588s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5129899978637695s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.2591977119445801s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.018935441970825s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.017319440841675s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2682816982269287s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 8.130073547363281e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 9.5367431640625e-06s
INFO | --- Analysis for eu-agencies-bodies took 12.255178928375244s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.1484832763671875e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.00033092498779296875s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.2627270221710205s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.0994415283203125e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 7.867813110351562e-06s
INFO | --- Analysis for eu-dgt-tm took 2.853447437286377s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.3392181396484375e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.28370189666748047s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020285606384277344s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.510185241699219e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 5.245208740234375e-06s
INFO | --- Analysis for eu-institutions took 5.406565189361572s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.7085251808166504s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2626967430114746s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.457069396972656e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.245208740234375e-06s
INFO | --- Analysis for eu-parliament-media took 6.171647071838379s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.8031260967254639s
Availability | VoID file availability check for EU Who Is Who took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2657806873321533s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.743171691894531e-05s
Believability | Calculation of trust value for EU Who Is Who took 5.4836273193359375e-06s
INFO | --- Analysis for eu-who-is-who took 8.520506143569946s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.7219784259796143s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0007500648498535156s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.28130316734313965s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.100799560546875e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 6.4373016357421875e-06s
INFO | --- Analysis for eumida-linked-data took 7.028255939483643s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.35558485984802246s
Availability | VoID file availability check for European Nature Information System took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.23931550979614258s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010967254638671875s
Believability | Calculation of trust value for European Nature Information System took 8.58306884765625e-06s
INFO | --- Analysis for eunis took 5.813766241073608s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 3.6696853637695312s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.255171537399292s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.390975952148438e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 7.62939453125e-06s
INFO | --- Analysis for eur-lex-rdf took 10.93987488746643s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.6769688129425049s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2639651298522949s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.0209352970123291s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.649162292480469e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 5.245208740234375e-06s
INFO | --- Analysis for eurobarometer-standard took 7.50900411605835s
Availability | SPARQL endpoint availability check for European Election Results took 0.7377607822418213s
Availability | VoID file availability check for European Election Results took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for European Election Results took 0.26825571060180664s
Reputation | Calculation of the PageRank for European Election Results took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.504753112792969e-05s
Believability | Calculation of trust value for European Election Results took 5.4836273193359375e-06s
INFO | --- Analysis for european-election-results took 7.431675910949707s
Availability | SPARQL endpoint availability check for EPO patents took 0.36995816230773926s
Availability | VoID file availability check for EPO patents took 0.0006670951843261719s
Extra | Recovery of all triples for EPO patents took 52.77041959762573s
Performance | Total latancy measurement for EPO patents took 0.8941731452941895s
Amount of data | Number of triples check for EPO patents took 90.19243621826172s
Versatility | Languages check for EPO patents took 120.08957815170288s
Interpretability | Number of blank nodes check for EPO patents took 90.29975152015686s
Interpretability | RDF structures check for EPO patents took 0.29142212867736816s
Versatility | Serialization formats check for EPO patents took 0.248399019241333s
Availability | RDF dump link check for EPO patents took 0.2273252010345459s
License | MR license check for EPO patents took 0.27002668380737305s
License | HR license check for EPO patents took 90.15895557403564s
Amount of data | Number of property check for EPO patents took 0.20410895347595215s
Understandability | Number of label check for EPO patents took 90.17445921897888s
Understandability | URI regex check for EPO patents took 0.6452181339263916s
Understandability | Vocabs check for EPO patents took 0.23892664909362793s
Verifiability | Authors check for EPO patents took 0.2453022003173828s
Verifiability | Publishers check for EPO patents took 0.2599306106567383s
Performance | Throughput check for EPO patents took 10.940425634384155s
Amount of data | Check the number of entities for EPO patents took 8.535385131835938e-05s
Verifiability | Contribs. check for EPO patents took 0.23289942741394043s
Interlinking | sameAs chians check for EPO patents took 0.1818232536315918s
Interlinking | skos check for EPO patents took 0.2960221767425537s
Interlinking | skos check for EPO patents took 0.19100737571716309s
Timeliness | dataset update frequency check for EPO patents took 0.1570889949798584s
Currency | Creation date check for EPO patents took 0.49919915199279785s
Currency | Modification date check for EPO patents took 0.34900927543640137s
Rep.Conc. | URIs length for EPO patents took 155.39325594902039s
Interoperability | New vocabularies check for EPO patents took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.19485807418823242s
Accuracy | Check Empty annotation labels for EPO patents took 18.281940698623657s
Accuracy | Check White space in annotation for EPO patents took 2.9872348308563232s
Accuracy | Check Datatype consistency for EPO patents took 5.10655665397644s
Consistency | Disjoint class check for EPO patents took 0.1843090057373047s
Consistency | Check Misplaced properties for EPO patents took 120.31032943725586s
Consistency | Check Ontology hijacking for EPO patents took 24.304737091064453s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.5873634815216064s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.41730570793152s
Conciseness | Check Extensional conciseness for EPO patents took 2.827463388442993s
Conciseness | Check Intensional conciseness for EPO patents took 0.3732113838195801s
Security | Sign check for EPO patents took 0.2665848731994629s
Availability | Check URIs Dereferenciability for EPO patents took 1.527632474899292s
Completeness | Calculation of interlinking completeness for EPO patents took 2.2228076457977295s
Reputation | Calculation of the PageRank for EPO patents took 0.02126002311706543s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.6689300537109375e-06s
Believability | Calculation of trust value for EPO patents took 1.2636184692382812e-05s
INFO | --- Analysis for European_Patent_Information took 1323.8920679092407s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.27547335624694824s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.02084493637084961s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for europeana-lod took 4.73544979095459s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.3392181396484375e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.30679869651794434s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.5367431640625e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.3909759521484375e-06s
INFO | --- Analysis for europeana-lod-v1 took 8.123113632202148s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.05548906326293945s
Availability | VoID file availability check for Europeana SPARQL took 0.00039196014404296875s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2497243881225586s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.887580871582031e-05s
Believability | Calculation of trust value for Europeana SPARQL took 9.059906005859375e-06s
INFO | --- Analysis for europeana-sparql took 4.294761419296265s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07784819602966309s
Availability | VoID file availability check for EuroSentiment took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.32712388038635254s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.814697265625e-05s
Believability | Calculation of trust value for EuroSentiment took 8.344650268554688e-06s
INFO | --- Analysis for eurosentiment took 3.7116811275482178s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.4345855712890625e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2733023166656494s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.677078247070312e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.245208740234375e-06s
INFO | --- Analysis for eurostat-rdf took 20.10530710220337s
Availability | SPARQL endpoint availability check for EuroVoc took 0.2854776382446289s
Availability | VoID file availability check for EuroVoc took 0.0006556510925292969s
Extra | Recovery of all triples for EuroVoc took 105.0846471786499s
Performance | Total latancy measurement for EuroVoc took 0.6296782493591309s
Amount of data | Number of triples check for EuroVoc took 80.3881733417511s
Interoperability | New terms check for EuroVoc took 92.67569160461426s
Versatility | Languages check for EuroVoc took 300.1372940540314s
Interpretability | Number of blank nodes check for EuroVoc took 1.5920886993408203s
Security | Check HTTPS for EuroVoc took 0.37543487548828125s
Interpretability | RDF structures check for EuroVoc took 0.7196841239929199s
Versatility | Serialization formats check for EuroVoc took 3.4511239528656006s
Availability | RDF dump link check for EuroVoc took 0.30597877502441406s
License | MR license check for EuroVoc took 0.26149797439575195s
License | HR license check for EuroVoc took 300.04876351356506s
Amount of data | Number of property check for EuroVoc took 0.19265151023864746s
Understandability | Number of label check for EuroVoc took 6.249191999435425s
Understandability | URI regex check for EuroVoc took 0.2708415985107422s
Understandability | Vocabs check for EuroVoc took 0.12067937850952148s
Verifiability | Authors check for EuroVoc took 0.20945239067077637s
Verifiability | Publishers check for EuroVoc took 0.24466943740844727s
Performance | Throughput check for EuroVoc took 10.536705493927002s
Amount of data | Check the number of entities for EuroVoc took 7.343292236328125e-05s
Verifiability | Contribs. check for EuroVoc took 0.2008969783782959s
Interlinking | sameAs chians check for EuroVoc took 11.298636198043823s
Interlinking | skos check for EuroVoc took 0.48923611640930176s
Interlinking | skos check for EuroVoc took 0.4747326374053955s
Timeliness | dataset update frequency check for EuroVoc took 0.3005096912384033s
Currency | Creation date check for EuroVoc took 0.5016365051269531s
Currency | Modification date check for EuroVoc took 0.24798107147216797s
Rep.Conc. | URIs length for EuroVoc took 575.8153953552246s
Interoperability | New vocabularies check for EuroVoc took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.170074462890625s
Accuracy | Check Functional Property for EuroVoc took 0.16229867935180664s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.16286039352416992s
Accuracy | Check Empty annotation labels for EuroVoc took 26.114686250686646s
Accuracy | Check White space in annotation for EuroVoc took 3.153108596801758s
Accuracy | Check Datatype consistency for EuroVoc took 2.636958599090576s
Consistency | Disjoint class check for EuroVoc took 0.14705586433410645s
Consistency | Check Misplaced properties for EuroVoc took 300.4775092601776s
Consistency | Misplaced classes for EuroVoc took 8.566159725189209s
Consistency | Check Ontology hijacking for EuroVoc took 34.69542336463928s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 12.230027675628662s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.2848358154297s
Conciseness | Check Extensional conciseness for EuroVoc took 3.029247283935547s
Conciseness | Check Intensional conciseness for EuroVoc took 0.5415010452270508s
Security | Sign check for EuroVoc took 0.15979242324829102s
Availability | Check URIs Dereferenciability for EuroVoc took 4.274996757507324s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.1293916702270508s
Reputation | Calculation of the PageRank for EuroVoc took 0.021297454833984375s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 7.009506225585938e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.430511474609375e-06s
Believability | Calculation of trust value for EuroVoc took 8.821487426757812e-06s
INFO | --- Analysis for eurovoc took 15141.488003253937s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.172325134277344e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.27155613899230957s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.021546125411987305s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.172325134277344e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 8.58306884765625e-06s
INFO | --- Analysis for eurovoc-in-skos took 4.4206767082214355s
Availability | SPARQL endpoint availability check for European Television Heritage took 7.510185241699219e-05s
Availability | VoID file availability check for European Television Heritage took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.26949548721313477s
Reputation | Calculation of the PageRank for European Television Heritage took 0.022648334503173828s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0012683868408203125s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 4.4345855712890625e-05s
Believability | Calculation of trust value for European Television Heritage took 9.059906005859375e-06s
INFO | --- Analysis for euscreen took 4.269244194030762s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.5299530029296875e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2626309394836426s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020924806594848633s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.054473876953125e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 6.198883056640625e-06s
INFO | --- Analysis for euskadi-farmacias took 6.386577367782593s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7913980484008789s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.27936458587646484s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.02091813087463379s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.2901763916015625e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 8.58306884765625e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.522729396820068s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.3305168151855469s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0013532638549804688s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.25392937660217285s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.021049976348876953s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.653236389160156e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 8.58306884765625e-06s
INFO | --- Analysis for eutc-productions took 6.748328924179077s
Availability | SPARQL endpoint availability check for EventMedia took 0.3602766990661621s
Availability | VoID file availability check for EventMedia took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for EventMedia took 0.27832865715026855s
Reputation | Calculation of the PageRank for EventMedia took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011205673217773438s
Believability | Calculation of trust value for EventMedia took 8.821487426757812e-06s
INFO | --- Analysis for event-media took 11.1653573513031s
Availability | SPARQL endpoint availability check for EventKG took 4.315376281738281e-05s
Availability | VoID file availability check for EventKG took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for EventKG took 0.2863435745239258s
Reputation | Calculation of the PageRank for EventKG took 0.02139568328857422s
Interlinking | Calculation of Degree of Connection for EventKG took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for EventKG took 9.179115295410156e-05s
Believability | Calculation of trust value for EventKG took 7.867813110351562e-06s
INFO | --- Analysis for eventkg took 4.973129510879517s
Availability | SPARQL endpoint availability check for Eventseer took 1.1113872528076172s
Availability | VoID file availability check for Eventseer took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2675790786743164s
Reputation | Calculation of the PageRank for Eventseer took 0.021082401275634766s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.7206878662109375e-05s
Believability | Calculation of trust value for Eventseer took 7.3909759521484375e-06s
INFO | --- Analysis for eventseer took 3.5308454036712646s
Availability | SPARQL endpoint availability check for Face Link took 4.2438507080078125e-05s
Availability | VoID file availability check for Face Link took 0.000400543212890625s
Completeness | Calculation of interlinking completeness for Face Link took 0.2670104503631592s
Reputation | Calculation of the PageRank for Face Link took 0.021237611770629883s
Interlinking | Calculation of Degree of Connection for Face Link took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0008769035339355469s
Interlinking | Calculation of Clustering coefficient for Face Link took 4.315376281738281e-05s
Believability | Calculation of trust value for Face Link took 7.3909759521484375e-06s
INFO | --- Analysis for Face_Link took 2.3467938899993896s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.100799560546875e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.24001383781433105s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.02120661735534668s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.695487976074219e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 8.344650268554688e-06s
INFO | --- Analysis for facebook-lids took 2.85489821434021s
Availability | SPARQL endpoint availability check for Fact Forge took 4.267692565917969e-05s
Availability | VoID file availability check for Fact Forge took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.26584744453430176s
Reputation | Calculation of the PageRank for Fact Forge took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.0994415283203125e-05s
Believability | Calculation of trust value for Fact Forge took 7.62939453125e-06s
INFO | --- Analysis for fact-forge took 2.9257712364196777s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6238718032836914s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002715587615966797s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 118.76967024803162s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9773342609405518s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.755137205123901s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 17.05072832107544s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.1649305820465s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.226280450820923s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.28285765647888184s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.848933696746826s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3282771110534668s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.7143478393554688s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2020058631897s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.31991147994995117s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6854100227355957s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0176587104797363s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4848611354827881s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19960379600524902s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.25987744331359863s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.061925649642944s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.963180541992188e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18254899978637695s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20026135444641113s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4936676025390625s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4556260108947754s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.3357696533203125s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4852478504180908s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22530102729797363s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 157.993812084198s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18451309204101562s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3987693786621094s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4490363597869873s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 47.34651970863342s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.691701650619507s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7469019889831543s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18080615997314453s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 89.1408212184906s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.49712872505188s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 38.73772954940796s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3264989852905273s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 87.6997754573822s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.762005090713501s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5280449390411377s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.014411211013794s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.983793497085571s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.5464365482330322s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.02115321159362793s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for FADN_(2019) took 2298.5804438591003s
Availability | SPARQL endpoint availability check for FAMEData took 6.890296936035156e-05s
Availability | VoID file availability check for FAMEData took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for FAMEData took 0.2769176959991455s
Reputation | Calculation of the PageRank for FAMEData took 0.02130913734436035s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for FAMEData took 0.00015735626220703125s
Believability | Calculation of trust value for FAMEData took 7.867813110351562e-06s
INFO | --- Analysis for famedata took 64.19216394424438s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.267692565917969e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.27283549308776855s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.393692016601562e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 6.198883056640625e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 9.477991580963135s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.23570799827575684s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.25144243240356445s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.021440505981445312s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010442733764648438s
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 3.469041347503662s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.3392181396484375e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.2634923458099365s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.0279159545898438e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for FAO_species took 3.2466092109680176s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.541442155838013s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.26915621757507324s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02093052864074707s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.887580871582031e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 9.775161743164062e-06s
INFO | --- Analysis for farmbio-chembl took 64.83999490737915s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.172325134277344e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.29104018211364746s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020330190658569336s
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.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 2.765655517578125e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 8.821487426757812e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 3.850235939025879s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.27945852279663086s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.027624845504760742s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0010194778442382812s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.409385681152344e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 7.867813110351562e-06s
INFO | --- Analysis for farolapp-dataset took 3.0470032691955566s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.2438507080078125e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.2527122497558594s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 2.9087066650390625e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 7.867813110351562e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 3.3281562328338623s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.291534423828125e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.23882484436035156s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.075599670410156e-05s
Believability | Calculation of trust value for I4.0-Onto took 6.4373016357421875e-06s
INFO | --- Analysis for fatimazahra took 2.7835426330566406s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.1961669921875e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.270249605178833s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.1948089599609375e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 8.106231689453125e-06s
INFO | --- Analysis for federal-economic-rdf took 2.8687174320220947s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.3392181396484375e-05s
Availability | VoID file availability check for Feed Wrapper took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.28229355812072754s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.0517578125e-05s
Believability | Calculation of trust value for Feed Wrapper took 3.075599670410156e-05s
INFO | --- Analysis for feedwrapper-lids took 2.949223279953003s
Availability | SPARQL endpoint availability check for FHIR STU3 took 7.43865966796875e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.25475645065307617s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.6941299438476562e-05s
Believability | Calculation of trust value for FHIR STU3 took 7.62939453125e-06s
INFO | --- Analysis for FHIR_STU3 took 2.5852980613708496s
Availability | SPARQL endpoint availability check for FiESTA took 5.14984130859375e-05s
Availability | VoID file availability check for FiESTA took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for FiESTA took 0.2790968418121338s
Reputation | Calculation of the PageRank for FiESTA took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.838539123535156e-05s
Believability | Calculation of trust value for FiESTA took 8.344650268554688e-06s
INFO | --- Analysis for fiesta took 12.651327133178711s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.601478576660156e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.25896167755126953s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02108478546142578s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.001190185546875s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.57763671875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.106231689453125e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.3423171043395996s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 5.030632019042969e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.25815343856811523s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.914138793945312e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.245208740234375e-06s
INFO | --- Analysis for finnish-municipalities took 4.610700368881226s
Availability | SPARQL endpoint availability check for firmao took 4.291534423828125e-05s
Availability | VoID file availability check for firmao took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for firmao took 0.2697737216949463s
Reputation | Calculation of the PageRank for firmao took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for firmao took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for firmao took 2.8848648071289062e-05s
Believability | Calculation of trust value for firmao took 7.3909759521484375e-06s
INFO | --- Analysis for firmao took 2.984004497528076s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.28690481185913086s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.920603036880493s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.19277358055114746s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.00025582313537597656s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 111.09077048301697s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.9582266807556152s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 8.258991479873657s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 13.042416334152222s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.24582529067993s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 3.312054395675659s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.29398322105407715s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 9.176900386810303s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.25218725204467773s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.6296069622039795s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.19859743118286s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.22507333755493164s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.8400444984436035s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.8963868618011475s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.46457576751708984s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.21442484855651855s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.2724592685699463s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 10.665809154510498s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.390975952148438e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.18829917907714844s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.19599580764770508s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.5523788928985596s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.46179771423339844s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 7.011811256408691s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.5268659591674805s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.22393584251403809s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 158.18088293075562s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.19835376739501953s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.3627893924713135s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.3788442611694336s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 48.36138415336609s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6979658603668213s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.6122355461120605s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.20197844505310059s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 80.15073275566101s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.606255769729614s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 37.18537449836731s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.2500340938568115s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 84.85769534111023s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.7406773567199707s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5556173324584961s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.8967595100402832s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 10.821460723876953s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.9736466407775879s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.02190566062927246s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 3.0994415283203125e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.528594970703125e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.3828277587890625e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2272.8946661949158s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.9591064453125e-05s
Availability | VoID file availability check for Fishes of Texas took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.6976287364959717s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 0.0001087188720703125s
Believability | Calculation of trust value for Fishes of Texas took 6.9141387939453125e-06s
INFO | --- Analysis for fishes-of-texas took 4.668110132217407s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.363059997558594e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.6912705898284912s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.083747863769531e-05s
Believability | Calculation of trust value for flickr? wrappr took 6.9141387939453125e-06s
INFO | --- Analysis for flickr-wrappr took 4.131808280944824s
Availability | SPARQL endpoint availability check for flickr.person took 4.172325134277344e-05s
Availability | VoID file availability check for flickr.person took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for flickr.person took 0.25672435760498047s
Reputation | Calculation of the PageRank for flickr.person took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0008623600006103516s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.218650817871094e-05s
Believability | Calculation of trust value for flickr.person took 7.3909759521484375e-06s
INFO | --- Analysis for flickr_person took 3.8670220375061035s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.076957702636719e-05s
Availability | VoID file availability check for flickr.videoobject took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.28148555755615234s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 2.7894973754882812e-05s
Believability | Calculation of trust value for flickr.videoobject took 9.5367431640625e-06s
INFO | --- Analysis for flickr_videoobject took 2.947814702987671s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.458427429199219e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.2583632469177246s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 2.8371810913085938e-05s
Believability | Calculation of trust value for Future land use simulation model took 6.9141387939453125e-06s
INFO | --- Analysis for FLUS took 7.0116777420043945s
Availability | SPARQL endpoint availability check for Fly-TED took 4.172325134277344e-05s
Availability | VoID file availability check for Fly-TED took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.2580239772796631s
Reputation | Calculation of the PageRank for Fly-TED took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.0517578125e-05s
Believability | Calculation of trust value for Fly-TED took 7.152557373046875e-06s
INFO | --- Analysis for fly-ted took 2.939601182937622s
Availability | SPARQL endpoint availability check for FlyAtlas took 5.555152893066406e-05s
Availability | VoID file availability check for FlyAtlas took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.27038002014160156s
Reputation | Calculation of the PageRank for FlyAtlas took 0.021246671676635742s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.218650817871094e-05s
Believability | Calculation of trust value for FlyAtlas took 1.2159347534179688e-05s
INFO | --- Analysis for flyatlas took 3.0097551345825195s
Availability | SPARQL endpoint availability check for Flybase took 1.6849920749664307s
Availability | VoID file availability check for Flybase took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Flybase took 0.25002336502075195s
Reputation | Calculation of the PageRank for Flybase took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for Flybase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.504753112792969e-05s
Believability | Calculation of trust value for Flybase took 7.3909759521484375e-06s
INFO | --- Analysis for flybase took 10.043187141418457s
Availability | SPARQL endpoint availability check for Flyted took 2.4263250827789307s
Availability | VoID file availability check for Flyted took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Flyted took 0.2734651565551758s
Reputation | Calculation of the PageRank for Flyted took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Flyted took 2.9325485229492188e-05s
Believability | Calculation of trust value for Flyted took 7.152557373046875e-06s
INFO | --- Analysis for flyted took 12.359671592712402s
Availability | SPARQL endpoint availability check for Foodista took 1.048525333404541s
Availability | VoID file availability check for Foodista took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Foodista took 0.2654411792755127s
Reputation | Calculation of the PageRank for Foodista took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9325485229492188e-05s
Believability | Calculation of trust value for Foodista took 6.9141387939453125e-06s
INFO | --- Analysis for foodista took 8.265984535217285s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.18484807014465332s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.250577449798584s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.581710815429688e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.152557373046875e-06s
INFO | --- Analysis for foodpedia took 2.5719375610351562s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.076957702636719e-05s
Availability | VoID file availability check for FORGE Course information took 0.0003991127014160156s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.26952457427978516s
Reputation | Calculation of the PageRank for FORGE Course information took 0.02134561538696289s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.266334533691406e-05s
Believability | Calculation of trust value for FORGE Course information took 7.3909759521484375e-06s
INFO | --- Analysis for forge-course-information took 2.908811330795288s
Availability | SPARQL endpoint availability check for FrameBase schema took 7.128715515136719e-05s
Availability | VoID file availability check for FrameBase schema took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.26925158500671387s
Reputation | Calculation of the PageRank for FrameBase schema took 0.021141767501831055s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.482269287109375e-05s
Believability | Calculation of trust value for FrameBase schema took 6.67572021484375e-06s
INFO | --- Analysis for framebase-schema took 2.9632740020751953s
Availability | SPARQL endpoint availability check for FrameNet took 4.172325134277344e-05s
Availability | VoID file availability check for FrameNet took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for FrameNet took 0.25904369354248047s
Reputation | Calculation of the PageRank for FrameNet took 0.021141529083251953s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.0517578125e-05s
Believability | Calculation of trust value for FrameNet took 7.62939453125e-06s
INFO | --- Analysis for framenet took 2.912071943283081s
Availability | SPARQL endpoint availability check for Framester took 4.220008850097656e-05s
Availability | VoID file availability check for Framester took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Framester took 0.26433873176574707s
Reputation | Calculation of the PageRank for Framester took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for Framester took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Framester took 7.486343383789062e-05s
Believability | Calculation of trust value for Framester took 6.67572021484375e-06s
INFO | --- Analysis for framester took 3.3778374195098877s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.200972318649292s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2577228546142578s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020900487899780273s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.96453857421875e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for frb-linked-data took 2.624068260192871s
Availability | SPARQL endpoint availability check for Freebase took 4.291534423828125e-05s
Availability | VoID file availability check for Freebase took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Freebase took 0.27521753311157227s
Reputation | Calculation of the PageRank for Freebase took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for Freebase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00028252601623535156s
Believability | Calculation of trust value for Freebase took 9.059906005859375e-06s
INFO | --- Analysis for freebase took 3.8275887966156006s
Availability | SPARQL endpoint availability check for Freeyork took 4.291534423828125e-05s
Availability | VoID file availability check for Freeyork took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2549617290496826s
Reputation | Calculation of the PageRank for Freeyork took 0.021254539489746094s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010633468627929688s
Believability | Calculation of trust value for Freeyork took 6.9141387939453125e-06s
INFO | --- Analysis for freeyork-org took 2.896444320678711s
Availability | SPARQL endpoint availability check for French School Program took 8.869171142578125e-05s
Availability | VoID file availability check for French School Program took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for French School Program took 0.26726698875427246s
Reputation | Calculation of the PageRank for French School Program took 0.020988941192626953s
Interlinking | Calculation of Degree of Connection for French School Program took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for French School Program took 2.9325485229492188e-05s
Believability | Calculation of trust value for French School Program took 7.62939453125e-06s
INFO | --- Analysis for french-school-program took 2.8860278129577637s
Availability | SPARQL endpoint availability check for French School System took 4.1484832763671875e-05s
Availability | VoID file availability check for French School System took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for French School System took 0.25403738021850586s
Reputation | Calculation of the PageRank for French School System took 0.021243810653686523s
Interlinking | Calculation of Degree of Connection for French School System took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for French School System took 3.2901763916015625e-05s
Believability | Calculation of trust value for French School System took 8.58306884765625e-06s
INFO | --- Analysis for french-school-system took 2.921348810195923s
Availability | SPARQL endpoint availability check for French TimeBank took 4.220008850097656e-05s
Availability | VoID file availability check for French TimeBank took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.27848076820373535s
Reputation | Calculation of the PageRank for French TimeBank took 0.02258133888244629s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.001027822494506836s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.6716461181640625e-05s
Believability | Calculation of trust value for French TimeBank took 7.62939453125e-06s
INFO | --- Analysis for french-timebank took 2.902522563934326s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.700953483581543s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.24780559539794922s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.653236389160156e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.357680082321167s
Availability | SPARQL endpoint availability check for DailyMed took 0.6571676731109619s
Availability | VoID file availability check for DailyMed took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for DailyMed took 0.25135159492492676s
Reputation | Calculation of the PageRank for DailyMed took 0.020669937133789062s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.226799011230469e-05s
Believability | Calculation of trust value for DailyMed took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.424933433532715s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7210757732391357s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2561359405517578s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.021176576614379883s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.845329284667969e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.346664667129517s
Availability | SPARQL endpoint availability check for Diseasome took 0.6646513938903809s
Availability | VoID file availability check for Diseasome took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Diseasome took 0.25089526176452637s
Reputation | Calculation of the PageRank for Diseasome took 0.020991086959838867s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010824203491210938s
Believability | Calculation of trust value for Diseasome took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.506040811538696s
Availability | SPARQL endpoint availability check for DrugBank took 0.6702382564544678s
Availability | VoID file availability check for DrugBank took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2938854694366455s
Reputation | Calculation of the PageRank for DrugBank took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011491775512695312s
Believability | Calculation of trust value for DrugBank took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.394252061843872s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.69118332862854s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.26690196990966797s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.0517578125e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.3589859008789062e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.279795408248901s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6767010688781738s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2454521656036377s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 8.20159912109375e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.241435766220093s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6848828792572021s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.27214956283569336s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.462501525878906e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-eures took 4.28403377532959s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6858978271484375s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2566699981689453s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.021136045455932617s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.00011420249938964844s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 4.915288925170898s
Availability | SPARQL endpoint availability check for MediCare took 0.679476261138916s
Availability | VoID file availability check for MediCare took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for MediCare took 0.2672996520996094s
Reputation | Calculation of the PageRank for MediCare took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for MediCare took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.00543212890625e-05s
Believability | Calculation of trust value for MediCare took 1.049041748046875e-05s
INFO | --- Analysis for fu-berlin-medicare took 4.928632497787476s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.6458308696746826s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.27516674995422363s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020985841751098633s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.605552673339844e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.3410491943359375s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6678390502929688s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.2978489398956299s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.226799011230469e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 6.4373016357421875e-06s
INFO | --- Analysis for fu-berlin-sider took 5.07277512550354s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6765429973602295s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2754669189453125s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 8.034706115722656e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.2519121170043945s
Availability | SPARQL endpoint availability check for fvdb took 4.553794860839844e-05s
Availability | VoID file availability check for fvdb took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for fvdb took 0.2765955924987793s
Reputation | Calculation of the PageRank for fvdb took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for fvdb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.9325485229492188e-05s
Believability | Calculation of trust value for fvdb took 6.9141387939453125e-06s
INFO | --- Analysis for fv took 12.442822217941284s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 8.797645568847656e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.2547731399536133s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.9087066650390625e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.867813110351562e-06s
INFO | --- Analysis for GACS took 3.1562392711639404s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 5.841255187988281e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.2544255256652832s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.1948089599609375e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 8.344650268554688e-06s
INFO | --- Analysis for galen_from_co-odeorg took 2.9474971294403076s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.38690185546875e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.25986576080322266s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.673004150390625e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 7.62939453125e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.324020862579346s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 5.1021575927734375e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.26073527336120605s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010037422180175781s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for garnicaplywood took 2.9465394020080566s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.57763671875e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.2681586742401123s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.942054748535156e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.3909759521484375e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.242239952087402s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.349808931350708s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2556159496307373s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.512901306152344e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for gemet took 5.0361292362213135s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.363059997558594e-05s
Availability | VoID file availability check for gemet-annotated took 0.0003590583801269531s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.23911476135253906s
Reputation | Calculation of the PageRank for gemet-annotated took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.4332275390625e-05s
Believability | Calculation of trust value for gemet-annotated took 7.152557373046875e-06s
INFO | --- Analysis for gemet-annotated took 2.949403762817383s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.8122537136077881s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2506897449493408s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020871639251708984s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0008296966552734375s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.867813110351562e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.141906976699829s
Availability | SPARQL endpoint availability check for Super Ontology took 1.093693494796753s
Availability | VoID file availability check for Super Ontology took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.25717830657958984s
Reputation | Calculation of the PageRank for Super Ontology took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Super Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 4.540247678756714s
Availability | SPARQL endpoint availability check for geo.place took 4.124641418457031e-05s
Availability | VoID file availability check for geo.place took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for geo.place took 0.2794685363769531s
Reputation | Calculation of the PageRank for geo.place took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for geo.place took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.409385681152344e-05s
Believability | Calculation of trust value for geo.place took 7.867813110351562e-06s
INFO | --- Analysis for geo_place took 2.8693690299987793s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.2438507080078125e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.2953312397003174s
Reputation | Calculation of the PageRank for Geographic detector model took 0.02112269401550293s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.075599670410156e-05s
Believability | Calculation of trust value for Geographic detector model took 8.106231689453125e-06s
INFO | --- Analysis for GeoDetector took 12.946335554122925s
Availability | SPARQL endpoint availability check for geodomainwn took 4.291534423828125e-05s
Availability | VoID file availability check for geodomainwn took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.2796618938446045s
Reputation | Calculation of the PageRank for geodomainwn took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.57763671875e-05s
Believability | Calculation of trust value for geodomainwn took 7.867813110351562e-06s
INFO | --- Analysis for geodomainwn took 6.706941366195679s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.267692565917969e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2680492401123047s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.295608520507812e-05s
Believability | Calculation of trust value for GeoEcuador took 7.3909759521484375e-06s
INFO | --- Analysis for geoecuador took 12.60142707824707s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.203648805618286s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.26085448265075684s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.890296936035156e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 7.3909759521484375e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.498512268066406s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.100799560546875e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.0007739067077636719s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.24206161499023438s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.62939453125e-06s
INFO | --- Analysis for geographic-openuplabs took 2.837678909301758s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5336613655090332s
Availability | VoID file availability check for GeoLinkedData took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.26064109802246094s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.726119995117188e-05s
Believability | Calculation of trust value for GeoLinkedData took 5.245208740234375e-06s
INFO | --- Analysis for geolinkeddata took 4.146648645401001s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.26172566413879395s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005288124084472656s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 11.31059980392456s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.39445018768310547s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1444382667541504s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.3056716918945312s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.2134251594543457s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.16963672637939453s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.18118596076965332s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.09719634056091309s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.09968256950378418s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.07731246948242188s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.10158801078796387s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.9666385650634766s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.10149860382080078s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.1062932014465332s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.1467733383178711s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.09400081634521484s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.06316065788269043s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08832287788391113s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.255197286605835s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 9.632110595703125e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06315374374389648s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.07663559913635254s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.09246253967285156s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07791924476623535s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06441354751586914s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16374707221984863s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.15947341918945312s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.490264892578125s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 9.129136323928833s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08751916885375977s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06866192817687988s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06825709342956543s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.33654189109802246s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007376909255981445s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.24121522903442383s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06829428672790527s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.21239948272705078s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5322635173797607s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.4579708576202393s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.488842248916626s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.679274082183838s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.18056106567382812s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07033133506774902s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0219318866729736s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.26668500900268555s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.368492126464844e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 9.300631523132324s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 72.64675569534302s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 8.225440979003906e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.00033855438232421875s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2732834815979004s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004730224609375s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.2636184692382812e-05s
INFO | --- Analysis for geonames-semantic-web took 3.242550849914551s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.363059997558594e-05s
Availability | VoID file availability check for Geospatial World  took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2686333656311035s
Reputation | Calculation of the PageRank for Geospatial World  took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0009479522705078125s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00024080276489257812s
Believability | Calculation of trust value for Geospatial World  took 8.344650268554688e-06s
INFO | --- Analysis for geospatialworld-net took 2.8882243633270264s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5970561504364014s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.29480600357055664s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013566017150878906s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for geospecies took 5.892491817474365s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.291534423828125e-05s
Availability | VoID file availability check for GeoWordNet took 0.0008273124694824219s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.26818346977233887s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.125999450683594e-05s
Believability | Calculation of trust value for GeoWordNet took 8.106231689453125e-06s
INFO | --- Analysis for geowordnet took 12.342870473861694s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.06395125389099121s
Availability | VoID file availability check for German labor law thesaurus took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.25214409828186035s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.963180541992188e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.5394251346588135s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.2594783306121826s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02080559730529785s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.291534423828125e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 8.58306884765625e-06s
INFO | --- Analysis for germlex took 2.8211922645568848s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.4808282852172852s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.26114320755004883s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0008387565612792969s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.822845458984375e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 7.3909759521484375e-06s
INFO | --- Analysis for gesis-thesoz took 5.757387161254883s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.3050036430358887s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.27900028228759766s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.748603820800781e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for getty-aat took 24.813896894454956s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 2.403045415878296s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2782931327819824s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.14984130859375e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.1444091796875e-05s
INFO | --- Analysis for getty-tgn took 23.690165996551514s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.2125532627105713s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.24790024757385254s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.409385681152344e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.4836273193359375e-06s
INFO | --- Analysis for gipuzkoademografia took 2.696965456008911s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.3392181396484375e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.25897717475891113s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.1948089599609375e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 7.867813110351562e-06s
INFO | --- Analysis for glastonbury-2011 took 5.641157865524292s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.4345855712890625e-05s
Availability | VoID file availability check for Global Change Information System took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.2604095935821533s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.170967102050781e-05s
Believability | Calculation of trust value for Global Change Information System took 7.3909759521484375e-06s
INFO | --- Analysis for global-change-information-system took 2.9228713512420654s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.792213439941406e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.2597503662109375s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 7.581710815429688e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.67572021484375e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.0662004947662354s
Availability | SPARQL endpoint availability check for Glottolog took 4.410743713378906e-05s
Availability | VoID file availability check for Glottolog took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Glottolog took 0.28421998023986816s
Reputation | Calculation of the PageRank for Glottolog took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.1975250244140625e-05s
Believability | Calculation of trust value for Glottolog took 7.867813110351562e-06s
INFO | --- Analysis for glottolog took 6.413164854049683s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 5.984306335449219e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.27069091796875s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020319223403930664s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010585784912109375s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 8.344650268554688e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 5.340453624725342s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 6.651878356933594e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.27938199043273926s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 3.0040740966796875e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 7.867813110351562e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.8292438983917236s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.291534423828125e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.00030803680419921875s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.28378796577453613s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020575284957885742s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.0040740966796875e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 6.9141387939453125e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.908783435821533s
Availability | SPARQL endpoint availability check for 1121 took 4.410743713378906e-05s
Availability | VoID file availability check for 1121 took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for 1121 took 0.265857458114624s
Reputation | Calculation of the PageRank for 1121 took 0.02104020118713379s
Interlinking | Calculation of Degree of Connection for 1121 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.24249267578125e-05s
Believability | Calculation of trust value for 1121 took 1.1682510375976562e-05s
INFO | --- Analysis for God_ took 2.735645294189453s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.315376281738281e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0007669925689697266s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.27707481384277344s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.245208740234375e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 7.867813110351562e-06s
INFO | --- Analysis for gold took 4.174747467041016s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.363059997558594e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.2920043468475342s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.914138793945312e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 6.198883056640625e-06s
INFO | --- Analysis for googleart-wrapper took 2.7503554821014404s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.1541304588317871s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2632756233215332s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.172325134277344e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 8.344650268554688e-06s
INFO | --- Analysis for govagribus-denmark took 34.86784100532532s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.35298752784729s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.27681422233581543s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.58306884765625e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.90348243713379s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.5469343662261963s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.28203725814819336s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.797645568847656e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.9604644775390625e-06s
INFO | --- Analysis for govtrack took 9.957937717437744s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.267692565917969e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.2670462131500244s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.91278076171875e-05s
Believability | Calculation of trust value for greek-administrative-geography took 7.3909759521484375e-06s
INFO | --- Analysis for greek-administrative-geography took 2.4754834175109863s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.2558119297027588s
Availability | VoID file availability check for Greek Wordnet took 0.0003612041473388672s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2511012554168701s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020920991897583008s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.100799560546875e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.1444091796875e-05s
INFO | --- Analysis for greek-wordnet took 2.6487972736358643s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 3.071744918823242s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.26848888397216797s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021203994750976562s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0015854835510253906s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.2636184692382812e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 7.3909759521484375e-06s
INFO | --- Analysis for greek_prisons_releases took 7.164595603942871s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.8030650615692139s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.26614856719970703s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.296966552734375e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.867813110351562e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.484665155410767s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 5.650520324707031e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2483985424041748s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.0209653377532959s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010466575622558594s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 4.702538728713989s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.7902634143829346s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.29233646392822266s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.8160552978515625e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 6.67572021484375e-06s
INFO | --- Analysis for grrp took 4.447291135787964s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.5026452541351318s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.27161431312561035s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020975828170776367s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.747245788574219e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.0067901611328125e-06s
INFO | --- Analysis for grrt took 4.008084058761597s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.713912010192871s
Availability | VoID file availability check for Geological Timescale took 0.0006909370422363281s
Extra | Recovery of all triples for Geological Timescale took 2.6175310611724854s
Performance | Total latancy measurement for Geological Timescale took 3.20080304145813s
Amount of data | Number of triples check for Geological Timescale took 0.49334168434143066s
Interoperability | New terms check for Geological Timescale took 1.7008488178253174s
Versatility | Languages check for Geological Timescale took 0.5221805572509766s
Interpretability | Number of blank nodes check for Geological Timescale took 0.44441699981689453s
Security | Check HTTPS for Geological Timescale took 0.3432140350341797s
Interpretability | RDF structures check for Geological Timescale took 0.4382131099700928s
Versatility | Serialization formats check for Geological Timescale took 0.9558839797973633s
Availability | RDF dump link check for Geological Timescale took 1.1546752452850342s
License | MR license check for Geological Timescale took 0.41483497619628906s
License | HR license check for Geological Timescale took 0.4568166732788086s
Amount of data | Number of property check for Geological Timescale took 0.400937557220459s
Understandability | Number of label check for Geological Timescale took 1.0033771991729736s
Understandability | URI regex check for Geological Timescale took 1.359337329864502s
Understandability | Vocabs check for Geological Timescale took 0.4069838523864746s
Verifiability | Authors check for Geological Timescale took 0.4211843013763428s
Verifiability | Publishers check for Geological Timescale took 2.0312111377716064s
Performance | Throughput check for Geological Timescale took 14.500987529754639s
Amount of data | Check the number of entities for Geological Timescale took 0.021048307418823242s
Verifiability | Contribs. check for Geological Timescale took 0.8965458869934082s
Interlinking | sameAs chians check for Geological Timescale took 0.9798409938812256s
Interlinking | skos check for Geological Timescale took 0.37133026123046875s
Interlinking | skos check for Geological Timescale took 0.9889142513275146s
Timeliness | dataset update frequency check for Geological Timescale took 0.409578800201416s
Currency | Creation date check for Geological Timescale took 2.474782943725586s
Currency | Modification date check for Geological Timescale took 0.4248809814453125s
Rep.Conc. | URIs length for Geological Timescale took 2.168698310852051s
Interoperability | New vocabularies check for Geological Timescale took 29.10864543914795s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.9429187774658203s
Accuracy | Check Functional Property for Geological Timescale took 1.0350677967071533s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9486815929412842s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.345787763595581s
Accuracy | Check White space in annotation for Geological Timescale took 0.015672683715820312s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07575821876525879s
Consistency | Disjoint class check for Geological Timescale took 0.9492654800415039s
Consistency | Check Misplaced properties for Geological Timescale took 0.8383224010467529s
Consistency | Misplaced classes for Geological Timescale took 0.5586757659912109s
Consistency | Check Ontology hijacking for Geological Timescale took 1.6473722457885742s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.145998477935791s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 1.5943150520324707s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.04986166954040527s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.45466017723083496s
Security | Sign check for Geological Timescale took 0.947432279586792s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.0485029220581055s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.38228321075439453s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.05718994140625e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 7.460626125335693s
Believability | Calculation of trust value for Geological Timescale took 7.867813110351562e-06s
INFO | --- Analysis for GTS took 137.80866694450378s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2517571449279785s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for GTS-ont took 2.7341244220733643s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.482269287109375e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.2652604579925537s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.123283386230469e-05s
Believability | Calculation of trust value for GUTSTOK  took 7.867813110351562e-06s
INFO | --- Analysis for Guillaume_Forget took 2.3684160709381104s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.315376281738281e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.2514667510986328s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.081031799316406e-05s
Believability | Calculation of trust value for Project Gutenberg took 7.867813110351562e-06s
INFO | --- Analysis for gutenberg took 8.792644023895264s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 5.269050598144531e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.26648950576782227s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.337860107421875e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 7.152557373046875e-06s
INFO | --- Analysis for gwa-ili took 5.196964740753174s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.315376281738281e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.2441389560699463s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.021076679229736328s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0009379386901855469s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.5762786865234375e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 7.867813110351562e-06s
INFO | --- Analysis for GWR took 13.818528175354004s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.4345855712890625e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.2541961669921875s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020445823669433594s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.0279159545898438e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 7.152557373046875e-06s
INFO | --- Analysis for HASM took 9.26521921157837s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 9.298324584960938e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.2739450931549072s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.0040740966796875e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.9404361248016357s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.478152275085449s
Availability | VoID file availability check for HealthCare Ontology took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.26718640327453613s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.4332275390625e-05s
Believability | Calculation of trust value for HealthCare Ontology took 7.152557373046875e-06s
INFO | --- Analysis for HealthCare_Ontology took 6.280594825744629s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.4345855712890625e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.26547741889953613s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.365776062011719e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 7.152557373046875e-06s
INFO | --- Analysis for heartfailure took 2.7023298740386963s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.790748357772827s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.2505459785461426s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0207517147064209s
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.6450881958007812e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.743171691894531e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 8.344650268554688e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 121.10051155090332s
Availability | SPARQL endpoint availability check for Hedatuz took 0.20729994773864746s
Availability | VoID file availability check for Hedatuz took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.27489137649536133s
Reputation | Calculation of the PageRank for Hedatuz took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.933906555175781e-05s
Believability | Calculation of trust value for Hedatuz took 6.67572021484375e-06s
INFO | --- Analysis for hedatuz took 2.9890716075897217s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.08723139762878418s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2528219223022461s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00013113021850585938s
Believability | Calculation of trust value for Hellenic Fire Brigade took 5.9604644775390625e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.472707986831665s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.0234982967376709s
Availability | VoID file availability check for Hellenic Police took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.25220632553100586s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012874603271484375s
Believability | Calculation of trust value for Hellenic Police took 5.7220458984375e-06s
INFO | --- Analysis for hellenic-police took 2.5156843662261963s
Availability | SPARQL endpoint availability check for Hermos took 5.793571472167969e-05s
Availability | VoID file availability check for Hermos took 0.00032591819763183594s
Completeness | Calculation of interlinking completeness for Hermos took 0.2493441104888916s
Reputation | Calculation of the PageRank for Hermos took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.956390380859375e-05s
Believability | Calculation of trust value for Hermos took 6.4373016357421875e-06s
INFO | --- Analysis for Hermos took 2.9167542457580566s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.3392181396484375e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2942335605621338s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.4332275390625e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 5.9604644775390625e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.3857581615448s
Availability | SPARQL endpoint availability check for HITO took 0.41701793670654297s
Availability | VoID file availability check for HITO took 0.00033855438232421875s
Extra | Recovery of all triples for HITO took 2.877152442932129s
Performance | Total latancy measurement for HITO took 0.7702786922454834s
Amount of data | Number of triples check for HITO took 0.14371919631958008s
Interoperability | New terms check for HITO took 1.384192705154419s
Versatility | Languages check for HITO took 0.17244768142700195s
Interpretability | Number of blank nodes check for HITO took 0.15794754028320312s
Interpretability | RDF structures check for HITO took 0.15811491012573242s
Versatility | Serialization formats check for HITO took 0.174424409866333s
Availability | RDF dump link check for HITO took 0.16522836685180664s
License | MR license check for HITO took 0.14607501029968262s
License | HR license check for HITO took 0.16064453125s
Amount of data | Number of property check for HITO took 0.1575164794921875s
Understandability | Number of label check for HITO took 0.1709272861480713s
Understandability | URI regex check for HITO took 0.32791876792907715s
Understandability | Vocabs check for HITO took 0.17262482643127441s
Verifiability | Authors check for HITO took 0.15721535682678223s
Verifiability | Publishers check for HITO took 0.15941977500915527s
Performance | Throughput check for HITO took 11.150150537490845s
Amount of data | Check the number of entities for HITO took 7.224082946777344e-05s
Verifiability | Contribs. check for HITO took 0.17041254043579102s
Interlinking | sameAs chians check for HITO took 0.14403867721557617s
Interlinking | skos check for HITO took 0.15733671188354492s
Interlinking | skos check for HITO took 0.14672088623046875s
Timeliness | dataset update frequency check for HITO took 0.16431903839111328s
Currency | Creation date check for HITO took 0.3034324645996094s
Currency | Modification date check for HITO took 0.30628466606140137s
Rep.Conc. | URIs length for HITO took 1.0005531311035156s
Interoperability | New vocabularies check for HITO took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.14835834503173828s
Accuracy | Check Functional Property for HITO took 0.1705176830291748s
Accuracy | Check Inverse Functional Property for HITO took 0.14729833602905273s
Accuracy | Check Empty annotation labels for HITO took 0.45856809616088867s
Accuracy | Check White space in annotation for HITO took 0.013494253158569336s
Accuracy | Check Datatype consistency for HITO took 0.0698096752166748s
Consistency | Disjoint class check for HITO took 0.18722963333129883s
Consistency | Check Misplaced properties for HITO took 0.4203166961669922s
Consistency | Misplaced classes for HITO took 0.3114960193634033s
Consistency | Check Ontology hijacking for HITO took 1.590869426727295s
Consistency | Check Invalid usage of undefined classes for HITO took 1.1543819904327393s
Consistency | Check Invalid usage of undefined properties for HITO took 1.3665835857391357s
Conciseness | Check Extensional conciseness for HITO took 0.061667680740356445s
Conciseness | Check Intensional conciseness for HITO took 0.15739130973815918s
Security | Sign check for HITO took 0.1554853916168213s
Availability | Check URIs Dereferenciability for HITO took 1517.7540264129639s
Completeness | Calculation of interlinking completeness for HITO took 1.405733346939087s
Reputation | Calculation of the PageRank for HITO took 0.021809101104736328s
Interlinking | Calculation of Degree of Connection for HITO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for HITO took 7.700920104980469e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.430511474609375e-06s
Believability | Calculation of trust value for HITO took 7.867813110351562e-06s
INFO | --- Analysis for hito took 1569.4935870170593s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 6.561152219772339s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.27408576011657715s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02115345001220703s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 4.029273986816406e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 7.3909759521484375e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 32.59112906455994s
Availability | SPARQL endpoint availability check for Homologene took 4.267692565917969e-05s
Availability | VoID file availability check for Homologene took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Homologene took 0.7337653636932373s
Reputation | Calculation of the PageRank for Homologene took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Homologene took 2.9802322387695312e-05s
Believability | Calculation of trust value for Homologene took 8.344650268554688e-06s
INFO | --- Analysis for homologene took 4.186597585678101s
Availability | SPARQL endpoint availability check for gseg took 4.1961669921875e-05s
Availability | VoID file availability check for gseg took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for gseg took 0.28098297119140625s
Reputation | Calculation of the PageRank for gseg took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for gseg took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for gseg took 3.147125244140625e-05s
Believability | Calculation of trust value for gseg took 7.3909759521484375e-06s
INFO | --- Analysis for hongse took 2.982954502105713s
Availability | SPARQL endpoint availability check for Noticias Universia took 0.00011348724365234375s
Availability | VoID file availability check for Noticias Universia took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.2580583095550537s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.123283386230469e-05s
Believability | Calculation of trust value for Noticias Universia took 6.9141387939453125e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.8983452320098877s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.124641418457031e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.25864148139953613s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.02106928825378418s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0009527206420898438s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.3855438232421875e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.62939453125e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.8787670135498047s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.6366627216339111s
Availability | VoID file availability check for COURAGE Dataset took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.27155113220214844s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0009758472442626953s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.457069396972656e-05s
Believability | Calculation of trust value for COURAGE Dataset took 7.152557373046875e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.144586801528931s
Availability | SPARQL endpoint availability check for RoadTrb took 4.267692565917969e-05s
Availability | VoID file availability check for RoadTrb took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2707173824310303s
Reputation | Calculation of the PageRank for RoadTrb took 0.02018284797668457s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.8848648071289062e-05s
Believability | Calculation of trust value for RoadTrb took 6.67572021484375e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.411325216293335s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2675187587738037s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 25.0827853679657s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 0.0005602836608886719s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.26877784729003906s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.075599670410156e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 7.62939453125e-06s
INFO | --- Analysis for http:pakistan.com took 2.3690810203552246s
Availability | SPARQL endpoint availability check for CEDICT took 5.14984130859375e-05s
Availability | VoID file availability check for CEDICT took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for CEDICT took 0.2647998332977295s
Reputation | Calculation of the PageRank for CEDICT took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.0279159545898438e-05s
Believability | Calculation of trust value for CEDICT took 7.152557373046875e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.628743648529053s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3595032691955566s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00034689903259277344s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2555248737335205s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.794929504394531e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.62939453125e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.332828521728516s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.172325134277344e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.24526214599609375s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 7.152557373046875e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.8493399620056152s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.2438507080078125e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.24756336212158203s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.02068924903869629s
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.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.0040740966796875e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.2971646785736084s
Availability | SPARQL endpoint availability check for Soccer Dataset took 5.745887756347656e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.24083375930786133s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020441532135009766s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.218650817871094e-05s
Believability | Calculation of trust value for Soccer Dataset took 6.67572021484375e-06s
INFO | --- Analysis for http:www.msm.com took 2.3565146923065186s
Availability | SPARQL endpoint availability check for Game Ontology took 4.982948303222656e-05s
Availability | VoID file availability check for Game Ontology took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.30501794815063477s
Reputation | Calculation of the PageRank for Game Ontology took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Game Ontology took 7.867813110351562e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.002697706222534s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.315376281738281e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26143765449523926s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.022264719009399414s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0008666515350341797s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.361701965332031e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.423783302307129s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 5.53131103515625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.262101411819458s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.67572021484375e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.4110517501831055s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.363059997558594e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2548856735229492s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.3603272438049316s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.291534423828125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.25577235221862793s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.3909759521484375e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.3672242164611816s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.4345855712890625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26648449897766113s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.4111671447753906s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.315376281738281e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2673954963684082s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02091503143310547s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.8356809616088867s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.2438507080078125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2636120319366455s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020648717880249023s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.239776611328125e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.3774526119232178s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.458427429199219e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.2731626033782959s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.123283386230469e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 7.3909759521484375e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 3.965883255004883s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.1586461067199707s
Availability | VoID file availability check for Bookkeeping took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.2502002716064453s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.170967102050781e-05s
Believability | Calculation of trust value for Bookkeeping took 7.62939453125e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.11897087097168s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Legal Ontology took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.251267671585083s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Legal Ontology took 7.152557373046875e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.842629909515381s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.482269287109375e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.24345135688781738s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.724761962890625e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.67572021484375e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.708484649658203s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.3392181396484375e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.26728272438049316s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0008709430694580078s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.361701965332031e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 7.152557373046875e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.5696299076080322s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.291534423828125e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.2721388339996338s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.0279159545898438e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 7.867813110351562e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.879863739013672s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.124641418457031e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2659108638763428s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020750761032104492s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 7.867813110351562e-06s
INFO | --- Analysis for hud-library-usagedata took 2.9290761947631836s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.512493371963501s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.24477767944335938s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010538101196289062s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 7.3909759521484375e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.410568714141846s
Availability | SPARQL endpoint availability check for IATE RDF took 5.8650970458984375e-05s
Availability | VoID file availability check for IATE RDF took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2665369510650635s
Reputation | Calculation of the PageRank for IATE RDF took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for IATE RDF took 8.106231689453125e-06s
INFO | --- Analysis for iate-rdf took 2.471684455871582s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.096087694168091s
Availability | VoID file availability check for IATI as Linked Data took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2995946407318115s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02109050750732422s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0009958744049072266s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 0.00010061264038085938s
Believability | Calculation of trust value for IATI as Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for iati-as-linked-data took 14.243852138519287s
Availability | SPARQL endpoint availability check for ICANE took 0.2617008686065674s
Availability | VoID file availability check for ICANE took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for ICANE took 0.27738022804260254s
Reputation | Calculation of the PageRank for ICANE took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for ICANE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for ICANE took 9.131431579589844e-05s
Believability | Calculation of trust value for ICANE took 5.4836273193359375e-06s
INFO | --- Analysis for icane took 3.5935378074645996s
Availability | SPARQL endpoint availability check for ichoose took 0.1275339126586914s
Availability | VoID file availability check for ichoose took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for ichoose took 0.2685434818267822s
Reputation | Calculation of the PageRank for ichoose took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for ichoose took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0008289813995361328s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.43865966796875e-05s
Believability | Calculation of trust value for ichoose took 7.62939453125e-06s
INFO | --- Analysis for ichoose took 42.1200749874115s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.48632121086120605s
Availability | VoID file availability check for The Iconology Dataset took 0.0007066726684570312s
Extra | Recovery of all triples for The Iconology Dataset took 4.885351896286011s
Performance | Total latancy measurement for The Iconology Dataset took 0.486250638961792s
Amount of data | Number of triples check for The Iconology Dataset took 0.1904611587524414s
Interoperability | New terms check for The Iconology Dataset took 1.316774845123291s
Versatility | Languages check for The Iconology Dataset took 0.5153515338897705s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.21693682670593262s
Interpretability | RDF structures check for The Iconology Dataset took 0.09317517280578613s
Versatility | Serialization formats check for The Iconology Dataset took 0.08768606185913086s
Availability | RDF dump link check for The Iconology Dataset took 0.08447933197021484s
License | MR license check for The Iconology Dataset took 0.09465599060058594s
License | HR license check for The Iconology Dataset took 0.23356127738952637s
Amount of data | Number of property check for The Iconology Dataset took 0.10258221626281738s
Understandability | Number of label check for The Iconology Dataset took 0.13939309120178223s
Understandability | URI regex check for The Iconology Dataset took 0.17003989219665527s
Understandability | Vocabs check for The Iconology Dataset took 0.08897829055786133s
Verifiability | Authors check for The Iconology Dataset took 0.0954749584197998s
Verifiability | Publishers check for The Iconology Dataset took 0.10981249809265137s
Performance | Throughput check for The Iconology Dataset took 10.387536764144897s
Amount of data | Check the number of entities for The Iconology Dataset took 0.000576019287109375s
Verifiability | Contribs. check for The Iconology Dataset took 0.09372997283935547s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09353995323181152s
Interlinking | skos check for The Iconology Dataset took 0.09021306037902832s
Interlinking | skos check for The Iconology Dataset took 0.08965873718261719s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09420466423034668s
Currency | Creation date check for The Iconology Dataset took 0.18011879920959473s
Currency | Modification date check for The Iconology Dataset took 0.18995881080627441s
Rep.Conc. | URIs length for The Iconology Dataset took 1.3623359203338623s
Interoperability | New vocabularies check for The Iconology Dataset took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08525967597961426s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.2715494632720947s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.01651597023010254s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.433887243270874s
Consistency | Disjoint class check for The Iconology Dataset took 0.09156656265258789s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.17480802536010742s
Consistency | Misplaced classes for The Iconology Dataset took 0.8709604740142822s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.5675091743469238s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.1687722206115723s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.2575123310089111s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2948606014251709s
Security | Sign check for The Iconology Dataset took 0.10282683372497559s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2600.0718133449554s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.498595952987671s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.02313089370727539s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.71661376953125e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for The Iconology Dataset took 8.344650268554688e-06s
INFO | --- Analysis for iconology-dataset took 2658.3580293655396s
Availability | SPARQL endpoint availability check for Identifiers.org took 7.081031799316406e-05s
Availability | VoID file availability check for Identifiers.org took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.25732851028442383s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 4.076957702636719e-05s
Believability | Calculation of trust value for Identifiers.org took 7.867813110351562e-06s
INFO | --- Analysis for identifiers-org took 5.136122703552246s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.458427429199219e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.26492905616760254s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 8.153915405273438e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 8.344650268554688e-06s
INFO | --- Analysis for idreffr took 4.8504884243011475s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.8714206218719482s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2572932243347168s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020785093307495117s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.221366882324219e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 7.62939453125e-06s
INFO | --- Analysis for ids took 3.7096805572509766s
Availability | SPARQL endpoint availability check for ietflang took 4.410743713378906e-05s
Availability | VoID file availability check for ietflang took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for ietflang took 0.2661933898925781s
Reputation | Calculation of the PageRank for ietflang took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for ietflang took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.863739013671875e-05s
Believability | Calculation of trust value for ietflang took 1.2636184692382812e-05s
INFO | --- Analysis for ietflang took 13.09438943862915s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.599780797958374s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.2700083255767822s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.020727157592773438s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 4.100799560546875e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 7.62939453125e-06s
INFO | --- Analysis for IGVLL took 5.904363393783569s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.45465683937072754s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0006420612335205078s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.9803225994110107s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 1.067350149154663s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.2220933437347412s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.4215233325958252s
Versatility | Languages check for 3LGM² IHE Ontology took 0.19475865364074707s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.20286774635314941s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.22458195686340332s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.2109205722808838s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.21882224082946777s
License | MR license check for 3LGM² IHE Ontology took 0.22657537460327148s
License | HR license check for 3LGM² IHE Ontology took 0.21757817268371582s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.19517064094543457s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.21099853515625s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.39928722381591797s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.21829581260681152s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.1961042881011963s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.20546722412109375s
Performance | Throughput check for 3LGM² IHE Ontology took 10.535149812698364s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 0.00011205673217773438s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.20583057403564453s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.19521284103393555s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20151901245117188s
Interlinking | skos check for 3LGM² IHE Ontology took 0.21416592597961426s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.2208542823791504s
Currency | Creation date check for 3LGM² IHE Ontology took 0.4148736000061035s
Currency | Modification date check for 3LGM² IHE Ontology took 0.4054567813873291s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8760659694671631s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.2313094139099121s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.19513416290283203s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.21412324905395508s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.34015440940856934s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.003678560256958008s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05231189727783203s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.19391345977783203s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.5084090232849121s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2890474796295166s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.5164356231689453s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.2195212841033936s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.475630283355713s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03130388259887695s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.21429967880249023s
Security | Sign check for 3LGM² IHE Ontology took 0.20897245407104492s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 429.6275384426117s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.7682955265045166s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.021053314208984375s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.170967102050781e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.430511474609375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 8.106231689453125e-06s
INFO | --- Analysis for IHE took 476.1099989414215s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.04873323440551758s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0003924369812011719s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.29111695289611816s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021008729934692383s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.337860107421875e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 8.821487426757812e-06s
INFO | --- Analysis for iislod-test took 3.428438186645508s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.220008850097656e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.26962709426879883s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.170967102050781e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 6.9141387939453125e-06s
INFO | --- Analysis for ILUSOC took 13.179223775863647s
Availability | SPARQL endpoint availability check for im@sparql took 6.234896421432495s
Availability | VoID file availability check for im@sparql took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for im@sparql took 0.26363706588745117s
Reputation | Calculation of the PageRank for im@sparql took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.0517578125e-05s
Believability | Calculation of trust value for im@sparql took 8.106231689453125e-06s
INFO | --- Analysis for im@sparql took 13.248138666152954s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.673004150390625e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.25608325004577637s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.021020889282226562s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.2901763916015625e-05s
Believability | Calculation of trust value for imagery bailingniao took 7.3909759521484375e-06s
INFO | --- Analysis for imagery_bailingniao took 3.401494264602661s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.0991339683532715s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.000568389892578125s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 22.97488784790039s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.515549898147583s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.375370502471924s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.37198543548584s
Versatility | Languages check for Imagesnippets Image Descriptions took 13.80665373802185s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 7.460450172424316s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6673986911773682s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7362926006317139s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7536296844482422s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7300200462341309s
License | MR license check for Imagesnippets Image Descriptions took 0.7361421585083008s
License | HR license check for Imagesnippets Image Descriptions took 10.670527219772339s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7140078544616699s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.7620837688446045s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.418222188949585s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7549066543579102s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7109193801879883s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7752902507781982s
Performance | Throughput check for Imagesnippets Image Descriptions took 17.307696104049683s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.2479248046875e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7140910625457764s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.726639986038208s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7265529632568359s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6720006465911865s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7498245239257812s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.485426902770996s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4706494808197021s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 28.882848262786865s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7362642288208008s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6800587177276611s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7416551113128662s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7539703845977783s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.512830495834351s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 17.30493187904358s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.213807582855225s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00015115737915039062s
Security | Sign check for Imagesnippets Image Descriptions took 0.7026040554046631s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.3373546600341797s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.1589956283569336s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 0.00010037422180175781s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.430511474609375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.049041748046875e-05s
INFO | --- Analysis for imagesnippets took 264.36979818344116s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.18180179595947266s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.807706356048584s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.988380432128906e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for imf-linked-data took 4.038666486740112s
Availability | SPARQL endpoint availability check for IMGpedia took 4.124641418457031e-05s
Availability | VoID file availability check for IMGpedia took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.23865509033203125s
Reputation | Calculation of the PageRank for IMGpedia took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.123283386230469e-05s
Believability | Calculation of trust value for IMGpedia took 7.3909759521484375e-06s
INFO | --- Analysis for imgpedia took 3.2711410522460938s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 5.459785461425781e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.28160786628723145s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0008780956268310547s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 3.266334533691406e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 7.3909759521484375e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 2.928494691848755s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.3392181396484375e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.2632410526275635s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.2159347534179688e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 7.152557373046875e-06s
INFO | --- Analysis for Imtiaz took 2.3654470443725586s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.410743713378906e-05s
Availability | VoID file availability check for Royalty Free Music took 0.00040459632873535156s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2916994094848633s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.2901763916015625e-05s
Believability | Calculation of trust value for Royalty Free Music took 7.867813110351562e-06s
INFO | --- Analysis for inaudio.org took 3.8453574180603027s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.6253204345703125e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2580580711364746s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.021080970764160156s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.147125244140625e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 8.344650268554688e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 3.503547191619873s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 7.843971252441406e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.2690243721008301s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 2.8848648071289062e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 7.3909759521484375e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 3.3918495178222656s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.398120641708374s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.30786633491516113s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02043771743774414s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 4.100091218948364s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.172325134277344e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2786099910736084s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 2.9325485229492188e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 6.67572021484375e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 3.0123603343963623s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.506111145019531e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2682642936706543s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010347366333007812s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 8.106231689453125e-06s
INFO | --- Analysis for ineverycrea took 38.206946849823s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 7.653236389160156e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.29317784309387207s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.560585021972656e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 7.152557373046875e-06s
INFO | --- Analysis for ineverycrea-argentina took 12.07086730003357s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 0.04511570930480957s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.2655627727508545s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02421283721923828s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0011591911315917969s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 9.560585021972656e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 8.106231689453125e-06s
INFO | --- Analysis for influence-tracker-dataset took 13.001942157745361s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.124641418457031e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.28635668754577637s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020930051803588867s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.528594970703125e-05s
Believability | Calculation of trust value for INSEMTIVES took 1.3828277587890625e-05s
INFO | --- Analysis for insemtives took 2.9266462326049805s
Availability | SPARQL endpoint availability check for instagram.person took 4.3392181396484375e-05s
Availability | VoID file availability check for instagram.person took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for instagram.person took 0.24851441383361816s
Reputation | Calculation of the PageRank for instagram.person took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for instagram.person took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for instagram.person took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.0040740966796875e-05s
Believability | Calculation of trust value for instagram.person took 7.62939453125e-06s
INFO | --- Analysis for instagram_person took 2.861739158630371s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.124641418457031e-05s
Availability | VoID file availability check for instagram.videoobject took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.27147912979125977s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020900487899780273s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0009598731994628906s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.600120544433594e-05s
Believability | Calculation of trust value for instagram.videoobject took 7.62939453125e-06s
INFO | --- Analysis for instagram_videoobject took 2.9294936656951904s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.26329803466796875s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub Countries took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-countries took 2.9897937774658203s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.5299530029296875e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.28182291984558105s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0009694099426269531s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.552436828613281e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.43401837348938s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.1961669921875e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.25876784324645996s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 2.9802322387695312e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-organizations took 2.9760828018188477s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub People took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.2362668514251709s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0010755062103271484s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.743171691894531e-05s
Believability | Calculation of trust value for Instance Hub People took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-people took 2.90730619430542s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.2652571201324463s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 3.9116227626800537s
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.0002522468566894531s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.26935434341430664s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.1948089599609375e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.875150680541992s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.27269577980041504s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.947190999984741s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.26892757415771484s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 2.956390380859375e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-crops took 3.021106004714966s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.24938702583312988s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 2.956390380859375e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.923274278640747s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.267692565917969e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.3009941577911377s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020916461944580078s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.9512178897857666s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.2590358257293701s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 2.9087066650390625e-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 2.957885265350342s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.843971252441406e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.25230884552001953s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 2.8848648071289062e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.867813110351562e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.9082744121551514s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.458427429199219e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00075531005859375s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.320004940032959s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020813703536987305s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.775161743164062e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.344650268554688e-06s
INFO | --- Analysis for interactivemaps-gnoss took 321.1613006591797s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.291534423828125e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.28269195556640625s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.0279159545898438e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 7.3909759521484375e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.974571943283081s
Availability | SPARQL endpoint availability check for intervalue took 0.15857672691345215s
Availability | VoID file availability check for intervalue took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for intervalue took 0.273517370223999s
Reputation | Calculation of the PageRank for intervalue took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for intervalue took 7.009506225585938e-05s
Believability | Calculation of trust value for intervalue took 7.62939453125e-06s
INFO | --- Analysis for intervalue took 2.632572889328003s
Availability | SPARQL endpoint availability check for Inztrow took 5.984306335449219e-05s
Availability | VoID file availability check for Inztrow took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2701706886291504s
Reputation | Calculation of the PageRank for Inztrow took 0.020778656005859375s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.0517578125e-05s
Believability | Calculation of trust value for Inztrow took 8.344650268554688e-06s
INFO | --- Analysis for Inztrow took 3.725147008895874s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2834618091583252s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.021568775177001953s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0009465217590332031s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 7.62939453125e-06s
INFO | --- Analysis for ipbes took 6.72418999671936s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.935264587402344e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2679789066314697s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020745038986206055s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.3392181396484375e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 7.62939453125e-06s
INFO | --- Analysis for iptc-newscodes took 3.502342939376831s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.124641418457031e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.2568635940551758s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.075599670410156e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 7.152557373046875e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.931208610534668s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.044302463531494s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0008144378662109375s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.27069091796875s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.00010061264038085938s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.62939453125e-06s
INFO | --- Analysis for iserve took 7.792801380157471s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.791188716888428s
Availability | VoID file availability check for ISIC V4 took 0.0009291172027587891s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2892327308654785s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.457069396972656e-05s
Believability | Calculation of trust value for ISIC V4 took 9.5367431640625e-06s
INFO | --- Analysis for isic-v4 took 116.53629660606384s
Availability | SPARQL endpoint availability check for Isidore took 4.267692565917969e-05s
Availability | VoID file availability check for Isidore took 0.00032329559326171875s
Completeness | Calculation of interlinking completeness for Isidore took 0.27074360847473145s
Reputation | Calculation of the PageRank for Isidore took 0.021789073944091797s
Interlinking | Calculation of Degree of Connection for Isidore took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0009903907775878906s
Interlinking | Calculation of Clustering coefficient for Isidore took 4.57763671875e-05s
Believability | Calculation of trust value for Isidore took 1.0728836059570312e-05s
INFO | --- Analysis for isidore took 2.9719221591949463s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 5.030632019042969e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2719569206237793s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.104873657226562e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 9.775161743164062e-06s
INFO | --- Analysis for isil-dbpedia took 4.476950407028198s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 6.818771362304688e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.24765491485595703s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020803451538085938s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.3909759521484375e-06s
INFO | --- Analysis for iso-3166-2-data took 2.8725507259368896s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 5.698204040527344e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.28563857078552246s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.021178483963012695s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.5762786865234375e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 9.059906005859375e-06s
INFO | --- Analysis for iso-639-oasis took 2.8356757164001465s
Availability | SPARQL endpoint availability check for ISOcat took 4.2438507080078125e-05s
Availability | VoID file availability check for ISOcat took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for ISOcat took 0.2883419990539551s
Reputation | Calculation of the PageRank for ISOcat took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for ISOcat took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISOcat took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for ISOcat took 7.081031799316406e-05s
Believability | Calculation of trust value for ISOcat took 7.3909759521484375e-06s
INFO | --- Analysis for isocat took 33.17136001586914s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.1961669921875e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.2662169933319092s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.528594970703125e-05s
Believability | Calculation of trust value for ISOcat-metadata took 7.867813110351562e-06s
INFO | --- Analysis for isocat-metadata took 4.820454120635986s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.315376281738281e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.26047730445861816s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.075599670410156e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 8.344650268554688e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.9405174255371094s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.25063085556030273s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006737709045410156s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.275919437408447s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8829731941223145s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.23828864097595215s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.943467140197754s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 93.04423546791077s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18567156791687012s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13165950775146484s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19637179374694824s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17163991928100586s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2289731502532959s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2485978603363037s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 93.02960181236267s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1781473159790039s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.54154372215271s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5435113906860352s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22353625297546387s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.25031518936157227s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15775251388549805s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.621214389801025s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.368492126464844e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24173665046691895s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.26967573165893555s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.49917078018188477s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.48769545555114746s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22469210624694824s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3175685405731201s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15224289894104004s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 15.460150003433228s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16981792449951172s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.153517484664917s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18653535842895508s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.910742521286011s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3094179630279541s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2626357078552246s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13265013694763184s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.834499835968018s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9619874954223633s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.977212429046631s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2215075492858887s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.922256231307983s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2878541946411133s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20809531211853027s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19759321212768555s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.613568782806396s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8957383632659912s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0209810733795166s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.441375732421875e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.62939453125e-06s
INFO | --- Analysis for ispra-lod-place took 472.4440665245056s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.2438507080078125e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.00035262107849121094s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.7360250949859619s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.2901763916015625e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.049041748046875e-05s
INFO | --- Analysis for ispra-lod-rmn took 4.772018671035767s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.1376650333404541s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0006930828094482422s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 8.862907886505127s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.775029182434082s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.20733904838562012s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.8973050117492676s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.92901825904846s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.15888333320617676s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.1105961799621582s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.20221877098083496s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.2033531665802002s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.18393182754516602s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.22441458702087402s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.88330435752869s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.1782071590423584s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.4190807342529297s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.49364256858825684s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.20608210563659668s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.2342820167541504s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.13569355010986328s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 11.021242141723633s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 9.298324584960938e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.23550772666931152s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.2849161624908447s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.46881937980651855s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4549117088317871s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.2128610610961914s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3315768241882324s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.17255687713623047s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 15.373902559280396s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.16871142387390137s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.16455864906311035s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.19719672203063965s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 4.654205799102783s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3065962791442871s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27738356590270996s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.16950035095214844s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.693225622177124s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9628725051879883s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 4.417892694473267s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.2191283702850342s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.748309135437012s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.29060816764831543s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.1646103858947754s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.17612004280090332s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 9.351483583450317s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.8815953731536865s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021291732788085938s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.528594970703125e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.4543533325195312e-05s
INFO | --- Analysis for ispra-lod-ron took 463.49639105796814s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.124641418457031e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2610592842102051s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.170967102050781e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-sc took 5.152780055999756s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.5896692276000977s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.24389028549194336s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.799003601074219e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 8.344650268554688e-06s
INFO | --- Analysis for issa-agritrop took 6.467951536178589s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.410743713378906e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2695155143737793s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020879268646240234s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.0994415283203125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 8.106231689453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.8805840015411377s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 6.914138793945312e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2753779888153076s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.170967102050781e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 8.344650268554688e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 2.9761264324188232s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 8.749961853027344e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.25283002853393555s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.02218484878540039s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0011637210845947266s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 4.291534423828125e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 9.298324584960938e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.623297929763794s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.7140605449676514s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.26796698570251465s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.021044492721557617s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 9.083747863769531e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 6.198883056640625e-06s
INFO | --- Analysis for istat-immigration took 4.13662052154541s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 5.173683166503906e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.27127790451049805s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.147125244140625e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 8.344650268554688e-06s
INFO | --- Analysis for istat-immigrazione took 2.9348888397216797s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.27243685722351074s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2684659957885742s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.022941112518310547s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.314018249511719e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 5.9604644775390625e-06s
INFO | --- Analysis for it-aifa-drug-prices took 2.945939302444458s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.5780975818634033s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.31315016746520996s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.02117919921875s
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.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 8.320808410644531e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 8.106231689453125e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 4.153458595275879s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.7206878662109375e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.2735738754272461s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.1948089599609375e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 8.821487426757812e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.913679599761963s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.315376281738281e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.2828996181488037s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.021198034286499023s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.2901763916015625e-05s
Believability | Calculation of trust value for IWMI Research Reports took 9.298324584960938e-06s
INFO | --- Analysis for iwmi-research-reports took 3.00148344039917s
Availability | SPARQL endpoint availability check for IWN took 4.267692565917969e-05s
Availability | VoID file availability check for IWN took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for IWN took 0.2701587677001953s
Reputation | Calculation of the PageRank for IWN took 0.02117776870727539s
Interlinking | Calculation of Degree of Connection for IWN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for IWN took 3.743171691894531e-05s
Believability | Calculation of trust value for IWN took 7.867813110351562e-06s
INFO | --- Analysis for iwn took 5.851966142654419s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.100799560546875e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.2763981819152832s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.020935773849487305s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.1948089599609375e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 8.58306884765625e-06s
INFO | --- Analysis for j-global-knowledge took 2.9788854122161865s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.291534423828125e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.0003211498260498047s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.25583314895629883s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.02095341682434082s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.1948089599609375e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 8.344650268554688e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.8345441818237305s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 7.377029895782471s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.000782012939453125s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2687399387359619s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 7.534027099609375e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 7.62939453125e-06s
INFO | --- Analysis for jamendo-dbtune took 22.93610978126526s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.291534423828125e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.254730224609375s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.649162292480469e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for japan-radioactivity-stat took 5.164449453353882s
Availability | SPARQL endpoint availability check for JEL Classification took 4.291534423828125e-05s
Availability | VoID file availability check for JEL Classification took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.25539588928222656s
Reputation | Calculation of the PageRank for JEL Classification took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.0040740966796875e-05s
Believability | Calculation of trust value for JEL Classification took 7.867813110351562e-06s
INFO | --- Analysis for jel-classification took 4.814323663711548s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1451256275177002s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.253279447555542s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 7.62939453125e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 6.691212892532349s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.13642144203186s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.26412057876586914s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.021041393280029297s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.463859558105469e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 7.3909759521484375e-06s
INFO | --- Analysis for jita took 539.9928076267242s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.553794860839844e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.28373146057128906s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020852088928222656s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.600120544433594e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 8.344650268554688e-06s
INFO | --- Analysis for jmdict took 4.87382960319519s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.047019004821777s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.6884427070617676s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.702278137207031e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.0251998901367188e-05s
INFO | --- Analysis for john-goodwins-family-tree took 65.75827121734619s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.506111145019531e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2805781364440918s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.2901763916015625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 7.3909759521484375e-06s
INFO | --- Analysis for jp-cos took 4.96725869178772s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.267692565917969e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.304842472076416s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0008227825164794922s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.124641418457031e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 7.62939453125e-06s
INFO | --- Analysis for jp-textbook took 4.843442678451538s
Availability | SPARQL endpoint availability check for JRC-Names took 4.2438507080078125e-05s
Availability | VoID file availability check for JRC-Names took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.31301116943359375s
Reputation | Calculation of the PageRank for JRC-Names took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007615089416503906s
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 5.064805269241333s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.7788252830505371s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.254364013671875s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.0208737850189209s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 7.05718994140625e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 6.9141387939453125e-06s
INFO | --- Analysis for jrc-names-mlode took 3.3430583477020264s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.220008850097656e-05s
Availability | VoID file availability check for JudaicaLink took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2825329303741455s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00011134147644042969s
Believability | Calculation of trust value for JudaicaLink took 1.1682510375976562e-05s
INFO | --- Analysis for judaicalink took 3.9669151306152344s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.1484832763671875e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.2723379135131836s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 2.9325485229492188e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 8.344650268554688e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.8830578327178955s
Availability | SPARQL endpoint availability check for KAKEN took 4.172325134277344e-05s
Availability | VoID file availability check for KAKEN took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for KAKEN took 0.277341365814209s
Reputation | Calculation of the PageRank for KAKEN took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.5762786865234375e-05s
Believability | Calculation of trust value for KAKEN took 7.3909759521484375e-06s
INFO | --- Analysis for kaken took 2.9774441719055176s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07927298545837402s
Availability | VoID file availability check for Kallikratis municipalities took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.276287317276001s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 0.0001010894775390625s
Believability | Calculation of trust value for Kallikratis municipalities took 5.7220458984375e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.485245704650879s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.220008850097656e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.2675321102142334s
Reputation | Calculation of the PageRank for Openflights Routes took 0.020978927612304688s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.0994415283203125e-05s
Believability | Calculation of trust value for Openflights Routes took 7.152557373046875e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.9108428955078125s
Availability | SPARQL endpoint availability check for EU Soccer League took 5.698204040527344e-05s
Availability | VoID file availability check for EU Soccer League took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2552804946899414s
Reputation | Calculation of the PageRank for EU Soccer League took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.528594970703125e-05s
Believability | Calculation of trust value for EU Soccer League took 7.152557373046875e-06s
INFO | --- Analysis for KG:Course_Submission took 3.539815902709961s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.363059997558594e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.29610157012939453s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.0967254638671875e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 6.9141387939453125e-06s
INFO | --- Analysis for KING took 2.625288486480713s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.38690185546875e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.26943421363830566s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.651878356933594e-05s
Believability | Calculation of trust value for Klappstuhlclub took 5.245208740234375e-06s
INFO | --- Analysis for klappstuhlclub took 12.504543781280518s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.940654516220093s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2670173645019531s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.651878356933594e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 7.3909759521484375e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.467639923095703s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.1484832763671875e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.3018221855163574s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.9325485229492188e-05s
Believability | Calculation of trust value for Knowledge Forest took 7.62939453125e-06s
INFO | --- Analysis for knowledge-map took 2.9514079093933105s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.76837158203125e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2548372745513916s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.9087066650390625e-05s
Believability | Calculation of trust value for Knowledge Forest took 7.3909759521484375e-06s
INFO | --- Analysis for KnowledgeFusion took 2.3694958686828613s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2586185932159424s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.02101612091064453s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.961822509765625e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.428246259689331s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.3392181396484375e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.23987984657287598s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 7.62939453125e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.892754316329956s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 8.845329284667969e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2856593132019043s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.075599670410156e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.1682510375976562e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.448499917984009s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.0531158447265625e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.27489686012268066s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.020775318145751953s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 2.9325485229492188e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 7.62939453125e-06s
INFO | --- Analysis for ktr took 2.9523558616638184s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.220008850097656e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2450423240661621s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 7.05718994140625e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.8848648071289062e-05s
Believability | Calculation of trust value for Informatics Studies took 6.198883056640625e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.984517812728882s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.09450340270996094s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.7008624076843262s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.600120544433594e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for kupkb took 9.301912069320679s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.267692565917969e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.26146721839904785s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 2.956390380859375e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 7.62939453125e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.9354348182678223s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.141054153442383s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0007750988006591797s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.27716732025146484s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.82012939453125e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.152557373046875e-06s
INFO | --- Analysis for l3s-dblp took 48.04616355895996s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.762045860290527s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2725217342376709s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020746469497680664s
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.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.937980651855469e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 8.344650268554688e-06s
INFO | --- Analysis for lak-dataset took 66.75720739364624s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.2059328556060791s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005643367767333984s
Extra | Recovery of all triples for  Language Name Authority List  took 129.81475281715393s
Performance | Total latancy measurement for  Language Name Authority List  took 0.5950953960418701s
Amount of data | Number of triples check for  Language Name Authority List  took 134.26558995246887s
Interoperability | New terms check for  Language Name Authority List  took 116.33495712280273s
Versatility | Languages check for  Language Name Authority List  took 300.07599663734436s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 1.0800211429595947s
Security | Check HTTPS for  Language Name Authority List  took 0.38344883918762207s
Interpretability | RDF structures check for  Language Name Authority List  took 0.7582037448883057s
Versatility | Serialization formats check for  Language Name Authority List  took 2.875915288925171s
Availability | RDF dump link check for  Language Name Authority List  took 0.16790270805358887s
License | MR license check for  Language Name Authority List  took 0.6191020011901855s
License | HR license check for  Language Name Authority List  took 300.0690915584564s
Amount of data | Number of property check for  Language Name Authority List  took 0.1928417682647705s
Understandability | Number of label check for  Language Name Authority List  took 5.845766067504883s
Understandability | URI regex check for  Language Name Authority List  took 0.25522375106811523s
Understandability | Vocabs check for  Language Name Authority List  took 0.10677504539489746s
Verifiability | Authors check for  Language Name Authority List  took 0.1786057949066162s
Verifiability | Publishers check for  Language Name Authority List  took 0.29178571701049805s
Performance | Throughput check for  Language Name Authority List  took 10.683079481124878s
Amount of data | Check the number of entities for  Language Name Authority List  took 7.081031799316406e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.20332789421081543s
Interlinking | sameAs chians check for  Language Name Authority List  took 8.54204273223877s
Interlinking | skos check for  Language Name Authority List  took 0.27800583839416504s
Interlinking | skos check for  Language Name Authority List  took 0.24405884742736816s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.26456212997436523s
Currency | Creation date check for  Language Name Authority List  took 0.9208240509033203s
Currency | Modification date check for  Language Name Authority List  took 0.17943072319030762s
Rep.Conc. | URIs length for  Language Name Authority List  took 516.3363649845123s
Interoperability | New vocabularies check for  Language Name Authority List  took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.12799453735351562s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.1757206916809082s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.2051999568939209s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 31.38240957260132s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.131028175354004s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.5925815105438232s
Consistency | Disjoint class check for  Language Name Authority List  took 0.14756059646606445s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.41640043258667s
Consistency | Misplaced classes for  Language Name Authority List  took 8.517668008804321s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 30.7706241607666s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 11.631578207015991s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.3786234855652s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.09023380279541s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.42587733268737793s
Security | Sign check for  Language Name Authority List  took 0.1546154022216797s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 3.998263359069824s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.5940048694610596s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021459579467773438s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 8.678436279296875e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.2159347534179688e-05s
INFO | --- Analysis for language-authority-list took 15441.003270149231s
Availability | SPARQL endpoint availability check for Lark took 384.2688090801239s
Availability | VoID file availability check for Lark took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for Lark took 0.9870350360870361s
Reputation | Calculation of the PageRank for Lark took 0.022191286087036133s
Interlinking | Calculation of Degree of Connection for Lark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Lark took 0.0001304149627685547s
Believability | Calculation of trust value for Lark took 7.62939453125e-06s
INFO | --- Analysis for LARK took 1677.4126875400543s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.40964841842651367s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.7034709453582764s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LASLA took 5.649594068527222s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.1961669921875e-05s
Availability | VoID file availability check for LATC Linksets took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.7208728790283203s
Reputation | Calculation of the PageRank for LATC Linksets took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 2.9802322387695312e-05s
Believability | Calculation of trust value for LATC Linksets took 1.52587890625e-05s
INFO | --- Analysis for latc-linksets took 4.358372688293457s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.4462714195251465s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.7014846801757812s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 4.915669202804565s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.3529493808746338s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.26918888092041016s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LatinAffectus took 4.814732789993286s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.3490467071533203s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.23857522010803223s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.172325134277344e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.463597536087036s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 5.5789947509765625e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.2761659622192383s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.021049022674560547s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.218650817871094e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.62939453125e-06s
INFO | --- Analysis for lcc took 3.279510974884033s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.267692565917969e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.37015438079833984s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011706352233886719s
Believability | Calculation of trust value for Library of Congress Subject Headings took 8.106231689453125e-06s
INFO | --- Analysis for lcsh took 6.366767168045044s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.38690185546875e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2836005687713623s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.0211641788482666s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 9.274482727050781e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 8.344650268554688e-06s
INFO | --- Analysis for lcsubjects took 2.599524974822998s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 0.0005972385406494141s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.24573206901550293s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020506620407104492s
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.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.0517578125e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 8.106231689453125e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.851712942123413s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.504157066345215s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.24978303909301758s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.291534423828125e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 8.106231689453125e-06s
INFO | --- Analysis for ldt@library took 34.960453510284424s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.124641418457031e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.2522444725036621s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.0040740966796875e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 8.821487426757812e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 3.3000872135162354s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 5.53131103515625e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.26520395278930664s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.02213597297668457s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0008838176727294922s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.4809112548828125e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 8.58306884765625e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 3.360990047454834s
Availability | SPARQL endpoint availability check for U ime Legije took 4.38690185546875e-05s
Availability | VoID file availability check for U ime Legije took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.24651503562927246s
Reputation | Calculation of the PageRank for U ime Legije took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 2.8848648071289062e-05s
Believability | Calculation of trust value for U ime Legije took 8.106231689453125e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.3189523220062256s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 5.626678466796875e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.26822662353515625s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 2.9325485229492188e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 8.58306884765625e-06s
INFO | --- Analysis for legislation-openuplabs took 2.876828670501709s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.3707246780395508s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.2734551429748535s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.020432710647583008s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.104873657226562e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 8.58306884765625e-06s
INFO | --- Analysis for LemmaBank took 4.671562194824219s
Availability | SPARQL endpoint availability check for lemonUby took 5.459785461425781e-05s
Availability | VoID file availability check for lemonUby took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for lemonUby took 0.25063395500183105s
Reputation | Calculation of the PageRank for lemonUby took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.29425048828125e-05s
Believability | Calculation of trust value for lemonUby took 8.106231689453125e-06s
INFO | --- Analysis for lemonuby took 3.3393824100494385s
Availability | SPARQL endpoint availability check for LemonWiktionary took 5.030632019042969e-05s
Availability | VoID file availability check for LemonWiktionary took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.24836444854736328s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.3855438232421875e-05s
Believability | Calculation of trust value for LemonWiktionary took 8.344650268554688e-06s
INFO | --- Analysis for lemonwiktionary took 4.370401382446289s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.4214799404144287s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.28317952156066895s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0008580684661865234s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for LewisShort took 3.9627773761749268s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.2616398334503174s
Availability | VoID file availability check for LEXIN-RDF took 0.00031375885009765625s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.24913406372070312s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 6.079673767089844e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.2874603271484375e-05s
INFO | --- Analysis for lexin-rdf took 6.029698610305786s
Availability | SPARQL endpoint availability check for lexinfo took 4.8160552978515625e-05s
Availability | VoID file availability check for lexinfo took 0.00038051605224609375s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2417445182800293s
Reputation | Calculation of the PageRank for lexinfo took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.821487426757812e-05s
Believability | Calculation of trust value for lexinfo took 6.9141387939453125e-06s
INFO | --- Analysis for lexinfo took 2.677809000015259s
Availability | SPARQL endpoint availability check for Lexvo took 4.1961669921875e-05s
Availability | VoID file availability check for Lexvo took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for Lexvo took 0.26120734214782715s
Reputation | Calculation of the PageRank for Lexvo took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for Lexvo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lexvo took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017213821411132812s
Believability | Calculation of trust value for Lexvo took 7.152557373046875e-06s
INFO | --- Analysis for lexvo took 2.913447618484497s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.2438507080078125e-05s
Availability | VoID file availability check for Lexvo.org took 0.000408172607421875s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.25103187561035156s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.867813110351562e-05s
Believability | Calculation of trust value for Lexvo.org took 7.867813110351562e-06s
INFO | --- Analysis for lexvo-org took 2.5356903076171875s
Availability | SPARQL endpoint availability check for LIBRIS took 0.2788681983947754s
Availability | VoID file availability check for LIBRIS took 0.00039386749267578125s
Extra | Recovery of all triples for LIBRIS took 20.863012552261353s
Performance | Total latancy measurement for LIBRIS took 0.7962493896484375s
Amount of data | Number of triples check for LIBRIS took 20.540645599365234s
Interoperability | New terms check for LIBRIS took 14.954737424850464s
Versatility | Languages check for LIBRIS took 0.20826196670532227s
Interpretability | Number of blank nodes check for LIBRIS took 300.05539083480835s
Security | Check HTTPS for LIBRIS took 0.39530372619628906s
Interpretability | RDF structures check for LIBRIS took 0.256333589553833s
Versatility | Serialization formats check for LIBRIS took 0.2357943058013916s
Availability | RDF dump link check for LIBRIS took 0.15416812896728516s
License | MR license check for LIBRIS took 0.24579739570617676s
License | HR license check for LIBRIS took 0.18042206764221191s
Amount of data | Number of property check for LIBRIS took 0.20746922492980957s
Understandability | Number of label check for LIBRIS took 0.33330225944519043s
Understandability | URI regex check for LIBRIS took 0.3679790496826172s
Understandability | Vocabs check for LIBRIS took 0.1719672679901123s
Verifiability | Authors check for LIBRIS took 0.15346646308898926s
Verifiability | Publishers check for LIBRIS took 0.1640932559967041s
Performance | Throughput check for LIBRIS took 10.631420135498047s
Amount of data | Check the number of entities for LIBRIS took 0.00011563301086425781s
Verifiability | Contribs. check for LIBRIS took 0.16470980644226074s
Interlinking | sameAs chians check for LIBRIS took 0.1709916591644287s
Interlinking | skos check for LIBRIS took 0.21548724174499512s
Interlinking | skos check for LIBRIS took 0.1493995189666748s
Timeliness | dataset update frequency check for LIBRIS took 0.17811942100524902s
Currency | Creation date check for LIBRIS took 1.4523053169250488s
Currency | Modification date check for LIBRIS took 0.6863629817962646s
Rep.Conc. | URIs length for LIBRIS took 83.29687261581421s
Interoperability | New vocabularies check for LIBRIS took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.19763898849487305s
Accuracy | Check Functional Property for LIBRIS took 0.2158820629119873s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.16619658470153809s
Accuracy | Check Datatype consistency for LIBRIS took 0.2670145034790039s
Consistency | Disjoint class check for LIBRIS took 0.23692631721496582s
Consistency | Check Misplaced properties for LIBRIS took 60.76042294502258s
Consistency | Misplaced classes for LIBRIS took 1.1878468990325928s
Consistency | Check Ontology hijacking for LIBRIS took 6.813728094100952s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1747055053710938s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 69.85436272621155s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2803528308868408s
Conciseness | Check Intensional conciseness for LIBRIS took 0.43337202072143555s
Security | Sign check for LIBRIS took 0.24699091911315918s
Availability | Check URIs Dereferenciability for LIBRIS took 9.466163873672485s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.7378926277160645s
Reputation | Calculation of the PageRank for LIBRIS took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.608268737792969e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.6689300537109375e-06s
Believability | Calculation of trust value for LIBRIS took 8.821487426757812e-06s
INFO | --- Analysis for libris took 1101.5090193748474s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06928324699401855s
Availability | VoID file availability check for Public Library of Veroia took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.6986207962036133s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 0.00012922286987304688s
Believability | Calculation of trust value for Public Library of Veroia took 8.58306884765625e-06s
INFO | --- Analysis for libver took 5.850492000579834s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.024309158325195312s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.24145746231079102s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 9.226799011230469e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.245208740234375e-06s
INFO | --- Analysis for lichfield-spending took 3.2374346256256104s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.1961669921875e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.25993967056274414s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02154064178466797s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.695487976074219e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 8.344650268554688e-06s
INFO | --- Analysis for lime took 7.27653169631958s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.38690185546875e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.27399230003356934s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007386207580566406s
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 7.867813110351562e-06s
INFO | --- Analysis for lingvoj took 5.169071912765503s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 7.43865966796875e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.25411462783813477s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.392333984375e-05s
Believability | Calculation of trust value for Linked Crunchbase took 7.3909759521484375e-06s
INFO | --- Analysis for linked-crunchbase took 3.718928575515747s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.136399030685425s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.000743865966796875s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.28669118881225586s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.605552673339844e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.867813110351562e-06s
INFO | --- Analysis for linked-drugs took 19.60623073577881s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.410743713378906e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.24839282035827637s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.00010514259338378906s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 5.245208740234375e-06s
INFO | --- Analysis for linked-edgar took 4.10278058052063s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 6.556510925292969e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.23911547660827637s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02096700668334961s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 0.00010633468627929688s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.62939453125e-06s
INFO | --- Analysis for linked-eurostat took 3.425004005432129s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.863739013671875e-05s
Availability | VoID file availability check for linked hypernyms took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2749946117401123s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.462501525878906e-05s
Believability | Calculation of trust value for linked hypernyms took 7.3909759521484375e-06s
INFO | --- Analysis for linked-hypernyms took 3.31526255607605s
Availability | SPARQL endpoint availability check for Linked Life Data took 223.6632001399994s
Availability | VoID file availability check for Linked Life Data took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.4826619625091553s
Reputation | Calculation of the PageRank for Linked Life Data took 0.02121567726135254s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 2.8133392333984375e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.863739013671875e-05s
Believability | Calculation of trust value for Linked Life Data took 8.106231689453125e-06s
INFO | --- Analysis for linked-life-data took 699.1243450641632s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.2756843566894531s
Availability | VoID file availability check for Linked Logainm took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.265186071395874s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.296966552734375e-05s
Believability | Calculation of trust value for Linked Logainm took 8.344650268554688e-06s
INFO | --- Analysis for linked-logainm took 5.9651196002960205s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.38690185546875e-05s
Availability | VoID file availability check for Linked NUTS took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.722956657409668s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02136993408203125s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.435943603515625e-05s
Believability | Calculation of trust value for Linked NUTS took 6.67572021484375e-06s
INFO | --- Analysis for linked-nuts took 3.280334949493408s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.7007122039794922s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 5.030632019042969e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 4.1416075229644775s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 2.7651922702789307s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.26508331298828125s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.528594970703125e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-camera took 5.201968669891357s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.1344075202941895s
Availability | VoID file availability check for Linked Open Commerce took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2560911178588867s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 2.956390380859375e-05s
Believability | Calculation of trust value for Linked Open Commerce took 9.059906005859375e-06s
INFO | --- Analysis for linked-open-commerce took 12.85871434211731s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.4964332580566406s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.277496337890625s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02124500274658203s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010609626770019531s
Believability | Calculation of trust value for Linked Open Data of Ecology took 7.62939453125e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 3.8681983947753906s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 6.937980651855469e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.24942564964294434s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.202957153320312e-05s
Believability | Calculation of trust value for Linked Open Numbers took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-numbers took 2.81674861907959s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.00035500526428222656s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.26235222816467285s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.8133392333984375e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.9604644775390625e-06s
INFO | --- Analysis for linked-open-piracy took 6.811225414276123s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.100799560546875e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.24701738357543945s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 2.86102294921875e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-senate took 2.8690457344055176s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 9.506709337234497s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.29492616653442383s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 5.793571472167969e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 74.45813059806824s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.410743713378906e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.24116158485412598s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 4.267692565917969e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.7220458984375e-06s
INFO | --- Analysis for linked-periodicals took 3.093306541442871s
Availability | SPARQL endpoint availability check for Linked Index took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Index took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2680842876434326s
Reputation | Calculation of the PageRank for Linked Index took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Linked Index took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.225440979003906e-05s
Believability | Calculation of trust value for Linked Index took 7.867813110351562e-06s
INFO | --- Analysis for linked-stockindex took 2.543506622314453s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.5156261920928955s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2810180187225342s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.838539123535156e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.3113021850585938e-05s
INFO | --- Analysis for linked-structured-product-labels took 11.564083576202393s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.967371940612793s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.25638246536254883s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.02260565757751465s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0011608600616455078s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 4.5299530029296875e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 7.867813110351562e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 3.437584638595581s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.118626594543457s
Availability | VoID file availability check for Linked TCGA took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.26398801803588867s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.749961853027344e-05s
Believability | Calculation of trust value for Linked TCGA took 8.821487426757812e-06s
INFO | --- Analysis for linked-tcga took 62.63899111747742s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.07205390930175781s
Availability | VoID file availability check for Linked User Feedback took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.23784494400024414s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02057480812072754s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.719329833984375e-05s
Believability | Calculation of trust value for Linked User Feedback took 6.9141387939453125e-06s
INFO | --- Analysis for linked-user-feedback took 2.538106679916382s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.3392181396484375e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0011146068572998047s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2788259983062744s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.748603820800781e-05s
Believability | Calculation of trust value for USPTO Patent data took 7.867813110351562e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.133586168289185s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2839224338531494s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020437240600585938s
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.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 8.344650268554688e-06s
INFO | --- Analysis for linked-web-apis took 2.959320068359375s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.076957702636719e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.26455235481262207s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.0994415283203125e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 8.58306884765625e-06s
INFO | --- Analysis for linkedarc took 2.970621347427368s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.035301923751831055s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2622990608215332s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 9.059906005859375e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.615835189819336s
Availability | SPARQL endpoint availability check for LinkedCT took 1.4296684265136719s
Availability | VoID file availability check for LinkedCT took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.26075005531311035s
Reputation | Calculation of the PageRank for LinkedCT took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.0001010894775390625s
Believability | Calculation of trust value for LinkedCT took 8.58306884765625e-06s
INFO | --- Analysis for linkedct took 5.114972352981567s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.1871497631072998s
Availability | VoID file availability check for LinkedGeoData took 0.0005304813385009766s
Extra | Recovery of all triples for LinkedGeoData took 15.235665559768677s
Performance | Total latancy measurement for LinkedGeoData took 0.67757248878479s
Amount of data | Number of triples check for LinkedGeoData took 49.64277219772339s
Interoperability | New terms check for LinkedGeoData took 92.08547711372375s
Versatility | Languages check for LinkedGeoData took 180.39989638328552s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.22643780708312988s
Security | Check HTTPS for LinkedGeoData took 0.2149343490600586s
Interpretability | RDF structures check for LinkedGeoData took 0.789630651473999s
Versatility | Serialization formats check for LinkedGeoData took 0.3293886184692383s
Availability | RDF dump link check for LinkedGeoData took 0.16031098365783691s
License | MR license check for LinkedGeoData took 0.5840823650360107s
License | HR license check for LinkedGeoData took 87.83342671394348s
Amount of data | Number of property check for LinkedGeoData took 0.3442952632904053s
Understandability | Number of label check for LinkedGeoData took 2.031111001968384s
Understandability | URI regex check for LinkedGeoData took 0.37453365325927734s
Understandability | Vocabs check for LinkedGeoData took 0.17503714561462402s
Verifiability | Authors check for LinkedGeoData took 0.16052746772766113s
Verifiability | Publishers check for LinkedGeoData took 0.13464999198913574s
Performance | Throughput check for LinkedGeoData took 10.698400974273682s
Amount of data | Check the number of entities for LinkedGeoData took 0.06556344032287598s
Verifiability | Contribs. check for LinkedGeoData took 1.938408613204956s
Interlinking | sameAs chians check for LinkedGeoData took 0.3232724666595459s
Interlinking | skos check for LinkedGeoData took 0.39806509017944336s
Interlinking | skos check for LinkedGeoData took 0.13198280334472656s
Timeliness | dataset update frequency check for LinkedGeoData took 0.37130308151245117s
Currency | Creation date check for LinkedGeoData took 0.49211978912353516s
Currency | Modification date check for LinkedGeoData took 2.3360097408294678s
Rep.Conc. | URIs length for LinkedGeoData took 272.1895999908447s
Interoperability | New vocabularies check for LinkedGeoData took 190.06727719306946s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.16375374794006348s
Accuracy | Check Functional Property for LinkedGeoData took 0.21135163307189941s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.18140125274658203s
Accuracy | Check Empty annotation labels for LinkedGeoData took 3.0745317935943604s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15947699546813965s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.1354672908782959s
Consistency | Disjoint class check for LinkedGeoData took 0.2381424903869629s
Consistency | Check Misplaced properties for LinkedGeoData took 180.77589225769043s
Consistency | Misplaced classes for LinkedGeoData took 0.6495704650878906s
Consistency | Check Ontology hijacking for LinkedGeoData took 4.509835958480835s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.1666665077209473s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.94069409370422s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.14988493919372559s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.3117039203643799s
Security | Sign check for LinkedGeoData took 0.6839900016784668s
Availability | Check URIs Dereferenciability for LinkedGeoData took 11.278601884841919s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.5839354991912842s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.02132701873779297s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.000118255615234375s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 182.0098569393158s
Believability | Calculation of trust value for LinkedGeoData took 7.3909759521484375e-06s
INFO | --- Analysis for linkedgeodata took 2520.5143904685974s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.1961669921875e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.8254249095916748s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.021117687225341797s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.0279159545898438e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 7.3909759521484375e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 5.247816801071167s
Availability | SPARQL endpoint availability check for LinkedLCCN took 16.91703963279724s
Availability | VoID file availability check for LinkedLCCN took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.6971437931060791s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010442733764648438s
Believability | Calculation of trust value for LinkedLCCN took 3.743171691894531e-05s
INFO | --- Analysis for linkedlccn took 28.29904055595398s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.2438507080078125e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2785344123840332s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.02126455307006836s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 4.38690185546875e-05s
Believability | Calculation of trust value for LinkedMarkMail took 7.3909759521484375e-06s
INFO | --- Analysis for linkedmarkmail took 2.4885640144348145s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.6389274597168s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.6931107044219971s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.000133514404296875s
Believability | Calculation of trust value for Linked Movie DataBase took 7.62939453125e-06s
INFO | --- Analysis for linkedmdb took 136.02183556556702s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.496396541595459s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.2676224708557129s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.390975952148438e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for linkedspending took 5.394391059875488s
Availability | SPARQL endpoint availability check for LinkedStats took 5.316734313964844e-05s
Availability | VoID file availability check for LinkedStats took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.25673913955688477s
Reputation | Calculation of the PageRank for LinkedStats took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 2.9325485229492188e-05s
Believability | Calculation of trust value for LinkedStats took 7.3909759521484375e-06s
INFO | --- Analysis for linkedstats took 4.089476823806763s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.172325134277344e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.285294771194458s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.0279159545898438e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 7.62939453125e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 3.364429235458374s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 5.53131103515625e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.2618134021759033s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.24249267578125e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 7.867813110351562e-06s
INFO | --- Analysis for linking-open-drug-data took 3.4827945232391357s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.05236053466796875s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.2688777446746826s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020741939544677734s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010848045349121094s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 7.62939453125e-06s
INFO | --- Analysis for linklion took 2.5168955326080322s
Availability | SPARQL endpoint availability check for Lion's Den took 4.172325134277344e-05s
Availability | VoID file availability check for Lion's Den took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.2539076805114746s
Reputation | Calculation of the PageRank for Lion's Den took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 0.0002942085266113281s
Believability | Calculation of trust value for Lion's Den took 9.059906005859375e-06s
INFO | --- Analysis for lionsden took 2.8552744388580322s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 35.61827850341797s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2793128490447998s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 4.887580871582031e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 41.35019659996033s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.124641418457031e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.2568857669830322s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 1.3113021850585938e-05s
INFO | --- Analysis for livtdm took 3.3767802715301514s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.076957702636719e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.2710607051849365s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.8371810913085938e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 7.62939453125e-06s
INFO | --- Analysis for livtdm2017 took 2.873326539993286s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.1961669921875e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.2649681568145752s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.62396240234375e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.62939453125e-06s
INFO | --- Analysis for lobi took 2.964836359024048s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.269695520401001s
Availability | VoID file availability check for lobid-organisations took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.2806820869445801s
Reputation | Calculation of the PageRank for lobid-organisations took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.5367431640625e-05s
Believability | Calculation of trust value for lobid-organisations took 7.62939453125e-06s
INFO | --- Analysis for lobid-organisations took 5.897748947143555s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.8595461845397949s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.25702714920043945s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.894371032714844e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 7.152557373046875e-06s
INFO | --- Analysis for lobid-resources took 7.876611709594727s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2582581043243408s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.605552673339844e-05s
Believability | Calculation of trust value for Linked Open Colors took 7.867813110351562e-06s
INFO | --- Analysis for loc took 7.124284505844116s
Availability | SPARQL endpoint availability check for Location Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Location Ontology took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.2845008373260498s
Reputation | Calculation of the PageRank for Location Ontology took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Location Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for Location_Ontology took 3.6818113327026367s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.3608405590057373s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.956390380859375e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 7.152557373046875e-06s
INFO | --- Analysis for locv took 34.57119154930115s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7412126064300537s
Availability | VoID file availability check for LOD-a-lot took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2737767696380615s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.8848648071289062e-05s
Believability | Calculation of trust value for LOD-a-lot took 7.62939453125e-06s
INFO | --- Analysis for lod-a-lot took 13.925275087356567s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.029273986816406e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.2687406539916992s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.0517578125e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 8.344650268554688e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.9171385765075684s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.00543212890625e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.26945996284484863s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.147125244140625e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 7.152557373046875e-06s
INFO | --- Analysis for lod-taiwan took 2.85866379737854s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.315376281738281e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2703719139099121s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.797645568847656e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 7.152557373046875e-06s
INFO | --- Analysis for lod2-project-wiki took 2.975752115249634s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.705274820327759s
Availability | VoID file availability check for LODAC BDLS took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.268587589263916s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.295608520507812e-05s
Believability | Calculation of trust value for LODAC BDLS took 7.867813110351562e-06s
INFO | --- Analysis for lodac-bdls took 13.882914543151855s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.315376281738281e-05s
Availability | VoID file availability check for LODRussia Math took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2912566661834717s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.86102294921875e-05s
Believability | Calculation of trust value for LODRussia Math took 7.152557373046875e-06s
INFO | --- Analysis for lodrussia-math took 2.9211976528167725s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.1484832763671875e-05s
Availability | VoID file availability check for LODRussia Nano took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.25109148025512695s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.0994415283203125e-05s
Believability | Calculation of trust value for LODRussia Nano took 8.106231689453125e-06s
INFO | --- Analysis for lodrussia-nano took 2.815554618835449s
Availability | SPARQL endpoint availability check for LODStats took 4.38690185546875e-05s
Availability | VoID file availability check for LODStats took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for LODStats took 0.2703416347503662s
Reputation | Calculation of the PageRank for LODStats took 0.020375728607177734s
Interlinking | Calculation of Degree of Connection for LODStats took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODStats took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.9802322387695312e-05s
Believability | Calculation of trust value for LODStats took 7.62939453125e-06s
INFO | --- Analysis for lodstats took 2.942228078842163s
Availability | SPARQL endpoint availability check for LODUM took 4.1484832763671875e-05s
Availability | VoID file availability check for LODUM took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for LODUM took 0.2520449161529541s
Reputation | Calculation of the PageRank for LODUM took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for LODUM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.956390380859375e-05s
Believability | Calculation of trust value for LODUM took 7.867813110351562e-06s
INFO | --- Analysis for lodum took 2.8231618404388428s
Availability | SPARQL endpoint availability check for lofd took 0.015575885772705078s
Availability | VoID file availability check for lofd took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for lofd took 0.25278162956237793s
Reputation | Calculation of the PageRank for lofd took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for lofd took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for lofd took 2.9325485229492188e-05s
Believability | Calculation of trust value for lofd took 7.152557373046875e-06s
INFO | --- Analysis for lofd took 2.390390396118164s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.41513895988464s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.25459861755371094s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021130084991455078s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 6.127357482910156e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 5.7220458984375e-06s
INFO | --- Analysis for loius took 585.5173857212067s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.2438507080078125e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.2667546272277832s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.021297693252563477s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 3.218650817871094e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 7.867813110351562e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 6.649249315261841s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.7920830249786377s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.26848268508911133s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 7.367134094238281e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.0067901611328125e-06s
INFO | --- Analysis for london-gazette took 5.03774619102478s
Availability | SPARQL endpoint availability check for Weather Stations took 4.553794860839844e-05s
Availability | VoID file availability check for Weather Stations took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.6773514747619629s
Reputation | Calculation of the PageRank for Weather Stations took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.320808410644531e-05s
Believability | Calculation of trust value for Weather Stations took 8.344650268554688e-06s
INFO | --- Analysis for los_metar took 4.542274236679077s
Availability | SPARQL endpoint availability check for Lotico took 0.9431519508361816s
Availability | VoID file availability check for Lotico took 0.00036907196044921875s
Completeness | Calculation of interlinking completeness for Lotico took 0.2622690200805664s
Reputation | Calculation of the PageRank for Lotico took 0.021193504333496094s
Interlinking | Calculation of Degree of Connection for Lotico took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.344650268554688e-05s
Believability | Calculation of trust value for Lotico took 7.867813110351562e-06s
INFO | --- Analysis for lotico took 7.721063852310181s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.3747715950012207s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0003197193145751953s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.25228333473205566s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 2.956390380859375e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 7.867813110351562e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 4.511685132980347s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6031172275543213s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00026607513427734375s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 119.96300172805786s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9695825576782227s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.021387577056885s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 13.694027662277222s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.17602038383484s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.279939889907837s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.26785969734191895s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 12.084491968154907s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2558436393737793s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6525468826293945s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2290790081024s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.309948205947876s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.2290279865264893s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6139426231384277s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4166603088378906s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2095470428466797s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2416384220123291s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.049455642700195s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.632110595703125e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2138066291809082s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21944570541381836s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4550807476043701s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.44097042083740234s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.293888330459595s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5197920799255371s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.24259567260742188s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 148.42993998527527s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21651339530944824s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.312549352645874s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.32073426246643066s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 43.35138201713562s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.683607339859009s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.638739824295044s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.201674222946167s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 81.78953003883362s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.556362390518188s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 33.35651230812073s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3133299350738525s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 84.40776824951172s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.748594045639038s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.580042839050293s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.7707846164703369s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.679961681365967s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8839437961578369s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.794929504394531e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for LPIS_(Poland) took 2265.480507850647s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18097257614135742s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.00027942657470703125s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 110.6843273639679s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0127110481262207s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.236938953399658s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 13.79934549331665s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.16525435447693s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.914118766784668s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.25605273246765137s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.868079423904419s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.33324742317199707s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6824855804443359s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2258052825928s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3184037208557129s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.591806650161743s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5760977268218994s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.28384971618652344s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19064116477966309s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2675502300262451s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.375128507614136s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.344650268554688e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21187210083007812s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19704008102416992s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.46346497535705566s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4599134922027588s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.762378454208374s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.46578335762023926s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2419745922088623s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 156.28024411201477s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19585728645324707s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.27765846252441406s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3386662006378174s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 44.93915152549744s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.687710762023926s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7197749614715576s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20928525924682617s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 85.24873518943787s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.55631947517395s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 34.42094922065735s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3196280002593994s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 80.84904313087463s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.851165294647217s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5921933650970459s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8605313301086426s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.593060493469238s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.4270975589752197s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.506111145019531e-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 8.106231689453125e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 2261.390667438507s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 5.8650970458984375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.6913919448852539s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.02106642723083496s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.218650817871094e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 8.344650268554688e-06s
INFO | --- Analysis for lremap-auth took 29.586557388305664s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.696846008300781e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.6876387596130371s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.021364212036132812s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.337860107421875e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 7.867813110351562e-06s
INFO | --- Analysis for lremap-conf took 16.629470586776733s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.4345855712890625e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.6910803318023682s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.0279159545898438e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 8.821487426757812e-06s
INFO | --- Analysis for lremap-ri took 16.202483654022217s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.5299530029296875e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.24882292747497559s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.123283386230469e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 8.344650268554688e-06s
INFO | --- Analysis for lremap-sub took 14.78935718536377s
Availability | SPARQL endpoint availability check for LSQ took 4.172325134277344e-05s
Availability | VoID file availability check for LSQ took 0.0003571510314941406s
Completeness | Calculation of interlinking completeness for LSQ took 0.2509326934814453s
Reputation | Calculation of the PageRank for LSQ took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.765655517578125e-05s
Believability | Calculation of trust value for LSQ took 3.123283386230469e-05s
INFO | --- Analysis for lsq took 3.468275308609009s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.46936655044555664s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.00034165382385253906s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2514665126800537s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for LucaniPharsalia took 4.32997465133667s
Availability | SPARQL endpoint availability check for Linked rules took 5.841255187988281e-05s
Availability | VoID file availability check for Linked rules took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Linked rules took 0.24117374420166016s
Reputation | Calculation of the PageRank for Linked rules took 0.0208585262298584s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked rules took 7.3909759521484375e-06s
INFO | --- Analysis for Luminaires_senlis took 2.738949775695801s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.2438507080078125e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.2619504928588867s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.266334533691406e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 6.9141387939453125e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.957979202270508s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.33149266242981s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.28135156631469727s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.021872520446777344s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0008320808410644531s
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 8.58306884765625e-06s
INFO | --- Analysis for makg took 65.3666877746582s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.291534423828125e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.25337934494018555s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.5762786865234375e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 7.152557373046875e-06s
INFO | --- Analysis for manchester-university-reading-lists took 4.441356658935547s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2528650760650635s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020721912384033203s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.9141387939453125e-06s
INFO | --- Analysis for manish took 2.376173496246338s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 3.981590270996094e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.2879478931427002s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.8133392333984375e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 7.867813110351562e-06s
INFO | --- Analysis for mapa-referencia-bogota took 3.415627956390381s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.220008850097656e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.24501466751098633s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.0517578125e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 1.239776611328125e-05s
INFO | --- Analysis for mapa-referencia-bogota-dc took 3.28802490234375s
Availability | SPARQL endpoint availability check for MARC Codes List took 7.43865966796875e-05s
Availability | VoID file availability check for MARC Codes List took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2708404064178467s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012183189392089844s
Believability | Calculation of trust value for MARC Codes List took 7.867813110351562e-06s
INFO | --- Analysis for marc-codes took 13.369288921356201s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 5.0067901611328125e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.00036144256591796875s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.26195287704467773s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02081131935119629s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.8623809814453125e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1682510375976562e-05s
INFO | --- Analysis for masc took 6.441142320632935s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.2438507080078125e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.26783251762390137s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 4.124641418457031e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.0013580322265625e-05s
INFO | --- Analysis for masc-bn-nif took 2.374969244003296s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.6105291843414307s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2554018497467041s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.147125244140625e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 7.62939453125e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.035170555114746s
Availability | SPARQL endpoint availability check for medline took 4.2438507080078125e-05s
Availability | VoID file availability check for medline took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for medline took 0.25780558586120605s
Reputation | Calculation of the PageRank for medline took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for medline took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for medline took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for medline took 8.797645568847656e-05s
Believability | Calculation of trust value for medline took 7.152557373046875e-06s
INFO | --- Analysis for medline took 9.185957193374634s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.7391068935394287s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.27124810218811035s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.985664367675781e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 7.62939453125e-06s
INFO | --- Analysis for meducator took 13.784427642822266s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 5.602836608886719e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.23985886573791504s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.9087066650390625e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 8.106231689453125e-06s
INFO | --- Analysis for mesh-finnish took 2.821399450302124s
Availability | SPARQL endpoint availability check for MeSH headings took 4.220008850097656e-05s
Availability | VoID file availability check for MeSH headings took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.25334930419921875s
Reputation | Calculation of the PageRank for MeSH headings took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 3.0517578125e-05s
Believability | Calculation of trust value for MeSH headings took 7.62939453125e-06s
INFO | --- Analysis for mesh_headings took 2.920375347137451s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2513265609741211s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0008492469787597656s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 7.62939453125e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.8691577911376953s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.124641418457031e-05s
Availability | VoID file availability check for MeSH pairs took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.26839137077331543s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020745515823364258s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 3.4332275390625e-05s
Believability | Calculation of trust value for MeSH pairs took 7.62939453125e-06s
INFO | --- Analysis for mesh_pairs took 2.8851397037506104s
Availability | SPARQL endpoint availability check for MeSH titles took 5.507469177246094e-05s
Availability | VoID file availability check for MeSH titles took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.29526638984680176s
Reputation | Calculation of the PageRank for MeSH titles took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.1948089599609375e-05s
Believability | Calculation of trust value for MeSH titles took 7.62939453125e-06s
INFO | --- Analysis for mesh_titles took 2.9820897579193115s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.2438507080078125e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2487034797668457s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020887136459350586s
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.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.0279159545898438e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 7.3909759521484375e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.841580629348755s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.058547973632812e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.2564520835876465s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0010564327239990234s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.933906555175781e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.106231689453125e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.906541109085083s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 5.745887756347656e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.26755237579345703s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.748603820800781e-05s
Believability | Calculation of trust value for MetaShare metadata model took 8.106231689453125e-06s
INFO | --- Analysis for metashare took 2.4831202030181885s
Availability | SPARQL endpoint availability check for MExiCo took 4.5299530029296875e-05s
Availability | VoID file availability check for MExiCo took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2695786952972412s
Reputation | Calculation of the PageRank for MExiCo took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.76837158203125e-05s
Believability | Calculation of trust value for MExiCo took 8.58306884765625e-06s
INFO | --- Analysis for mexico took 22.549625873565674s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.7321841716766357s
Availability | VoID file availability check for Coronavirus dataset took 0.0002613067626953125s
Extra | Recovery of all triples for Coronavirus dataset took 13.39383864402771s
Performance | Total latancy measurement for Coronavirus dataset took 3.4813787937164307s
Amount of data | Number of triples check for Coronavirus dataset took 1.1388230323791504s
Interoperability | New terms check for Coronavirus dataset took 2.5605225563049316s
Versatility | Languages check for Coronavirus dataset took 10.046842575073242s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.6246209144592285s
Interpretability | RDF structures check for Coronavirus dataset took 1.5540201663970947s
Versatility | Serialization formats check for Coronavirus dataset took 0.5327274799346924s
Availability | RDF dump link check for Coronavirus dataset took 0.4981687068939209s
License | MR license check for Coronavirus dataset took 0.5482540130615234s
License | HR license check for Coronavirus dataset took 38.711946964263916s
Amount of data | Number of property check for Coronavirus dataset took 0.5256078243255615s
Understandability | Number of label check for Coronavirus dataset took 2.0198071002960205s
Understandability | URI regex check for Coronavirus dataset took 1.007443904876709s
Understandability | Vocabs check for Coronavirus dataset took 1.2251262664794922s
Verifiability | Authors check for Coronavirus dataset took 2.2403135299682617s
Verifiability | Publishers check for Coronavirus dataset took 0.4938344955444336s
Performance | Throughput check for Coronavirus dataset took 15.499561548233032s
Amount of data | Check the number of entities for Coronavirus dataset took 0.00011134147644042969s
Verifiability | Contribs. check for Coronavirus dataset took 1.5216269493103027s
Interlinking | sameAs chians check for Coronavirus dataset took 1.5381791591644287s
Interlinking | skos check for Coronavirus dataset took 7.709784984588623s
Interlinking | skos check for Coronavirus dataset took 0.491530179977417s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5000650882720947s
Currency | Creation date check for Coronavirus dataset took 1.731947660446167s
Currency | Modification date check for Coronavirus dataset took 1.0132803916931152s
Rep.Conc. | URIs length for Coronavirus dataset took 10.308852910995483s
Interoperability | New vocabularies check for Coronavirus dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5179743766784668s
Accuracy | Check Functional Property for Coronavirus dataset took 0.750896692276001s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.719980001449585s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.7320451736450195s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022889137268066406s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.0273895263671875s
Consistency | Disjoint class check for Coronavirus dataset took 1.0564959049224854s
Consistency | Check Misplaced properties for Coronavirus dataset took 11.903317213058472s
Consistency | Misplaced classes for Coronavirus dataset took 0.6201939582824707s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.9122886657714844s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.1558449268341064s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.539221286773682s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.031804561614990234s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 1.5793306827545166s
Security | Sign check for Coronavirus dataset took 0.5060527324676514s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 4789.534168481827s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.2100937366485596s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.024239063262939453s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 5.7697296142578125e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 3.5762786865234375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.4066696166992188e-05s
INFO | --- Analysis for micro-coronavirus took 5022.897144079208s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0003914833068847656s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.6756081581115723s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010848045349121094s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 9.57240343093872s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.27817249298095703s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010943412780761719s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for mismuseos-gnoss took 10.09300971031189s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.08926796913146973s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.7131443023681641s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.482269287109375e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.62939453125e-06s
INFO | --- Analysis for mlsa took 3.8578081130981445s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.172325134277344e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.24644732475280762s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.647804260253906e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 7.3909759521484375e-06s
INFO | --- Analysis for model took 33.70171141624451s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.291534423828125e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0006766319274902344s
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.28098464012145996s
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.020632266998291016s
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 9.775161743164062e-06s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 2.9802322387695312e-05s
Believability | Calculation of trust value for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 7.3909759521484375e-06s
INFO | --- Analysis for model1 took 17.87341618537903s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.1484832763671875e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.26216769218444824s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.8848648071289062e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 7.62939453125e-06s
INFO | --- Analysis for mond took 3.3227145671844482s
Availability | SPARQL endpoint availability check for MONDIS took 4.124641418457031e-05s
Availability | VoID file availability check for MONDIS took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for MONDIS took 0.2707490921020508s
Reputation | Calculation of the PageRank for MONDIS took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.8371810913085938e-05s
Believability | Calculation of trust value for MONDIS took 9.059906005859375e-06s
INFO | --- Analysis for mondis took 2.961632490158081s
Availability | SPARQL endpoint availability check for Monumentos took 4.3392181396484375e-05s
Availability | VoID file availability check for Monumentos took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Monumentos took 0.25017690658569336s
Reputation | Calculation of the PageRank for Monumentos took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.0040740966796875e-05s
Believability | Calculation of trust value for Monumentos took 8.344650268554688e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.916121482849121s
Availability | SPARQL endpoint availability check for MORElab took 1.05466628074646s
Availability | VoID file availability check for MORElab took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for MORElab took 0.2588646411895752s
Reputation | Calculation of the PageRank for MORElab took 0.020852327346801758s
Interlinking | Calculation of Degree of Connection for MORElab took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.702278137207031e-05s
Believability | Calculation of trust value for MORElab took 8.344650268554688e-06s
INFO | --- Analysis for morelab took 4.6576457023620605s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.0425667762756348s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.24020719528198242s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.797645568847656e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 8.344650268554688e-06s
INFO | --- Analysis for msc took 6.151329278945923s
Availability | SPARQL endpoint availability check for Multext-East took 4.410743713378906e-05s
Availability | VoID file availability check for Multext-East took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for Multext-East took 0.269273042678833s
Reputation | Calculation of the PageRank for Multext-East took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Multext-East took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.314018249511719e-05s
Believability | Calculation of trust value for Multext-East took 7.62939453125e-06s
INFO | --- Analysis for multext-east took 2.3087053298950195s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.0531158447265625e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.27162790298461914s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 2.9087066650390625e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 8.106231689453125e-06s
INFO | --- Analysis for multilingualeulaw took 2.9326043128967285s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.363059997558594e-05s
Availability | VoID file availability check for Multimedia Lab took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.25635695457458496s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.314018249511719e-05s
Believability | Calculation of trust value for Multimedia Lab took 7.152557373046875e-06s
INFO | --- Analysis for multimedia-lab took 2.409867525100708s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.1484832763671875e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.2733592987060547s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 2.9802322387695312e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 1.2636184692382812e-05s
INFO | --- Analysis for munich-offener-haushalt took 2.8785417079925537s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.701002597808838s
Availability | VoID file availability check for Muninn World War I took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.25823020935058594s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0010676383972167969s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 0.0001087188720703125s
Believability | Calculation of trust value for Muninn World War I took 8.58306884765625e-06s
INFO | --- Analysis for muninn-world-war-i took 10.27448296546936s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.1484832763671875e-05s
Availability | VoID file availability check for Musei Italiani took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.26737403869628906s
Reputation | Calculation of the PageRank for Musei Italiani took 0.020891427993774414s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.0994415283203125e-05s
Believability | Calculation of trust value for Musei Italiani took 8.106231689453125e-06s
INFO | --- Analysis for musei-italiani took 2.885483741760254s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 5.817413330078125e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007963180541992188s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.7992968559265137s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.021577119827270508s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010943412780761719s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for museosespania-gnoss took 171.88489365577698s
Availability | SPARQL endpoint availability check for Italian Museums took 1.7635624408721924s
Availability | VoID file availability check for Italian Museums took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.27083802223205566s
Reputation | Calculation of the PageRank for Italian Museums took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.463859558105469e-05s
Believability | Calculation of trust value for Italian Museums took 7.3909759521484375e-06s
INFO | --- Analysis for museums-in-italy took 4.277955532073975s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.172325134277344e-05s
Availability | VoID file availability check for MusicBrainz took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.25055742263793945s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.0279159545898438e-05s
Believability | Calculation of trust value for MusicBrainz took 6.9141387939453125e-06s
INFO | --- Analysis for musicbrainz_ took 2.8781213760375977s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.124641418457031e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.2617228031158447s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.9325485229492188e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.152557373046875e-06s
INFO | --- Analysis for musicnet_codex took 2.884885311126709s
Availability | SPARQL endpoint availability check for Muziekweb took 0.503082275390625s
Availability | VoID file availability check for Muziekweb took 0.0006616115570068359s
Extra | Recovery of all triples for Muziekweb took 1.9858729839324951s
Performance | Total latancy measurement for Muziekweb took 1.4548296928405762s
Amount of data | Number of triples check for Muziekweb took 0.3274385929107666s
Interoperability | New terms check for Muziekweb took 1.5605401992797852s
Versatility | Languages check for Muziekweb took 57.943782329559326s
Interpretability | Number of blank nodes check for Muziekweb took 0.305711030960083s
Interpretability | RDF structures check for Muziekweb took 0.855262041091919s
Versatility | Serialization formats check for Muziekweb took 0.28055834770202637s
Availability | RDF dump link check for Muziekweb took 0.3166840076446533s
License | MR license check for Muziekweb took 0.5777971744537354s
License | HR license check for Muziekweb took 12.911839008331299s
Amount of data | Number of property check for Muziekweb took 0.30867552757263184s
Understandability | Number of label check for Muziekweb took 0.37508678436279297s
Understandability | URI regex check for Muziekweb took 0.6379446983337402s
Understandability | Vocabs check for Muziekweb took 0.3283731937408447s
Verifiability | Authors check for Muziekweb took 0.32462525367736816s
Verifiability | Publishers check for Muziekweb took 0.37106800079345703s
Performance | Throughput check for Muziekweb took 11.286138534545898s
Amount of data | Check the number of entities for Muziekweb took 7.176399230957031e-05s
Verifiability | Contribs. check for Muziekweb took 0.30725526809692383s
Interlinking | sameAs chians check for Muziekweb took 0.2917919158935547s
Interlinking | skos check for Muziekweb took 0.29120349884033203s
Interlinking | skos check for Muziekweb took 0.2777371406555176s
Timeliness | dataset update frequency check for Muziekweb took 0.31811952590942383s
Currency | Creation date check for Muziekweb took 0.7054970264434814s
Currency | Modification date check for Muziekweb took 0.6718556880950928s
Rep.Conc. | URIs length for Muziekweb took 1.9025518894195557s
Interoperability | New vocabularies check for Muziekweb took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.2713472843170166s
Accuracy | Check Functional Property for Muziekweb took 0.38399362564086914s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.3956139087677002s
Accuracy | Check Empty annotation labels for Muziekweb took 0.9677333831787109s
Accuracy | Check White space in annotation for Muziekweb took 0.02788400650024414s
Accuracy | Check Datatype consistency for Muziekweb took 0.02956080436706543s
Consistency | Disjoint class check for Muziekweb took 0.5239427089691162s
Consistency | Check Misplaced properties for Muziekweb took 1.1699514389038086s
Consistency | Check Ontology hijacking for Muziekweb took 2.0162274837493896s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 2.0529606342315674s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.5208444595336914s
Conciseness | Check Extensional conciseness for Muziekweb took 0.034789085388183594s
Conciseness | Check Intensional conciseness for Muziekweb took 0.31290245056152344s
Security | Sign check for Muziekweb took 0.26911139488220215s
Availability | Check URIs Dereferenciability for Muziekweb took 1810.4234266281128s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.398780345916748s
Reputation | Calculation of the PageRank for Muziekweb took 0.021383285522460938s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 0.00011777877807617188s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.6689300537109375e-06s
Believability | Calculation of trust value for Muziekweb took 8.821487426757812e-06s
INFO | --- Analysis for muziekweb took 1943.5399651527405s
Availability | SPARQL endpoint availability check for myExperiment took 0.34172964096069336s
Availability | VoID file availability check for myExperiment took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for myExperiment took 0.26991987228393555s
Reputation | Calculation of the PageRank for myExperiment took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00012040138244628906s
Believability | Calculation of trust value for myExperiment took 3.886222839355469e-05s
INFO | --- Analysis for my-experiment took 4.827608346939087s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.07084774971008301s
Availability | VoID file availability check for My Family Lineage took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.7013716697692871s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.821487426757812e-05s
Believability | Calculation of trust value for My Family Lineage took 3.409385681152344e-05s
INFO | --- Analysis for my-family-lineage took 4.870066165924072s
Availability | SPARQL endpoint availability check for My ontology test took 0.5147202014923096s
Availability | VoID file availability check for My ontology test took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for My ontology test took 0.27286243438720703s
Reputation | Calculation of the PageRank for My ontology test took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.0040740966796875e-05s
Believability | Calculation of trust value for My ontology test took 8.344650268554688e-06s
INFO | --- Analysis for myontologytest took 3.9282760620117188s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.220008850097656e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.3081991672515869s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020928621292114258s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010395050048828125s
Believability | Calculation of trust value for myopenlink dataspaces took 7.867813110351562e-06s
INFO | --- Analysis for myopenlink-dataspaces took 2.727735757827759s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.158369541168213s
Availability | VoID file availability check for N-Lex as Linked Data took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.25872111320495605s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.081031799316406e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 11.367920160293579s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.02914571762085s
Availability | VoID file availability check for NAICS 2007 took 0.0009169578552246094s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.6940925121307373s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.076957702636719e-05s
Believability | Calculation of trust value for NAICS 2007 took 5.9604644775390625e-06s
INFO | --- Analysis for naics-2007 took 125.99922680854797s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.4149329662323s
Availability | VoID file availability check for NAICS 2012 took 0.0009658336639404297s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.25982022285461426s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.698204040527344e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.4836273193359375e-06s
INFO | --- Analysis for naics-2012 took 125.56002712249756s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.262345552444458s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.1021575927734375e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for nalt took 3.3849260807037354s
Availability | SPARQL endpoint availability check for Usernames  took 4.267692565917969e-05s
Availability | VoID file availability check for Usernames  took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Usernames  took 0.26502561569213867s
Reputation | Calculation of the PageRank for Usernames  took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.075599670410156e-05s
Believability | Calculation of trust value for Usernames  took 7.62939453125e-06s
INFO | --- Analysis for Names took 2.5581552982330322s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 2.101853132247925s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007333755493164062s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 0.9797089099884033s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.7482306957244873s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 13.26116681098938s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 22.173285007476807s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.3603217601776123s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.855254411697388s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3593463897705078s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.39456915855407715s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3935110569000244s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.3491799831390381s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3522472381591797s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.8153874874115s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.905118465423584s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 5.479939937591553s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.703052282333374s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.32072925567626953s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.41324567794799805s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.356823205947876s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.385153532028198s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 0.0001537799835205078s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.3262448310852051s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.47837305068969727s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.5205104351043701s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.4407563209533691s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3681509494781494s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1044604778289795s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7851974964141846s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.971799373626709s
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.4244699478149414s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.34944987297058105s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.32575416564941406s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.39662837982177734s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.00078582763671875s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010247230529785156s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.41915249824523926s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7038278579711914s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.38373851776123047s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.5377979278564453s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.1596479415893555s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.552384614944458s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0005772113800048828s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.4311354160308838s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.157487154006958s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.7501232624053955s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 9.5367431640625e-07s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 5.4836273193359375e-06s
INFO | --- Analysis for national-diet-library-authorities took 234.71486854553223s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.3118019104003906s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006871223449707031s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.425025463104248s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.9384005069732666s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.849299430847168s
Interoperability | New terms check for National Diet Library of Japan subject headings took 27.19058346748352s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.44968461990356445s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.825355768203735s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3468191623687744s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.35102343559265137s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.37600040435791016s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.33469152450561523s
License | MR license check for National Diet Library of Japan subject headings took 0.3897407054901123s
License | HR license check for National Diet Library of Japan subject headings took 91.77533626556396s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.9149916172027588s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.0514867305755615s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7476809024810791s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.3614835739135742s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.41482996940612793s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.4039149284362793s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.519490242004395s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.511543273925781e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.3728768825531006s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.49317455291748047s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.3987584114074707s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.481649398803711s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.3473844528198242s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1109435558319092s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7160446643829346s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.9404311180114746s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.41870903968811035s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.4116368293762207s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.4006533622741699s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.38397955894470215s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0003311634063720703s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0004754066467285156s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.36747050285339355s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7725977897644043s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3661768436431885s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.5698161125183105s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.169626235961914s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.5921571254730225s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0005745887756347656s
Security | Sign check for National Diet Library of Japan subject headings took 0.37765049934387207s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 3.951977252960205s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.41228747367858887s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02120184898376465s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 9.059906005859375e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 236.35544729232788s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.141223669052124s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.6895711421966553s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.021174907684326172s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.9591064453125e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 7.62939453125e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 7.021374940872192s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.4345855712890625e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2723062038421631s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.022258758544921875s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0011267662048339844s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.608268737792969e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.344650268554688e-06s
INFO | --- Analysis for Naturopathy took 4.6593451499938965s
Availability | SPARQL endpoint availability check for Naturopathy took 5.602836608886719e-05s
Availability | VoID file availability check for Naturopathy took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.2708394527435303s
Reputation | Calculation of the PageRank for Naturopathy took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.0994415283203125e-05s
Believability | Calculation of trust value for Naturopathy took 1.239776611328125e-05s
INFO | --- Analysis for naturopathy2 took 3.348191022872925s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.26063013076782227s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for NCI Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for nci-thesaurus took 2.9433915615081787s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.4122698307037354s
Availability | VoID file availability check for COVID-19 Data took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.25536298751831055s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.123283386230469e-05s
Believability | Calculation of trust value for COVID-19 Data took 6.4373016357421875e-06s
INFO | --- Analysis for NCMI-COVID-19 took 9.74389123916626s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.392763376235962s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.26653528213500977s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.02067875862121582s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2159347534179688e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 7.152557373046875e-06s
INFO | --- Analysis for NCMICOVID-19 took 14.399860858917236s
Availability | SPARQL endpoint availability check for NDF-RT took 7.748603820800781e-05s
Availability | VoID file availability check for NDF-RT took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.29190850257873535s
Reputation | Calculation of the PageRank for NDF-RT took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.123283386230469e-05s
Believability | Calculation of trust value for NDF-RT took 1.1444091796875e-05s
INFO | --- Analysis for ndf-rt took 2.869220018386841s
Availability | SPARQL endpoint availability check for Near took 4.2438507080078125e-05s
Availability | VoID file availability check for Near took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Near took 0.24469232559204102s
Reputation | Calculation of the PageRank for Near took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for Near took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Near took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Near took 9.441375732421875e-05s
Believability | Calculation of trust value for Near took 7.62939453125e-06s
INFO | --- Analysis for near took 9.021220684051514s
Availability | SPARQL endpoint availability check for Neel took 4.100799560546875e-05s
Availability | VoID file availability check for Neel took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for Neel took 0.254741907119751s
Reputation | Calculation of the PageRank for Neel took 0.02085590362548828s
Interlinking | Calculation of Degree of Connection for Neel took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neel took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Neel took 3.218650817871094e-05s
Believability | Calculation of trust value for Neel took 3.1948089599609375e-05s
INFO | --- Analysis for neel took 2.9569315910339355s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.5299530029296875e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.26473164558410645s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020960569381713867s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.147125244140625e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 7.152557373046875e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.8923091888427734s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.1484832763671875e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.26359987258911133s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.24249267578125e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 6.9141387939453125e-06s
INFO | --- Analysis for neurolex-wiki took 2.3291690349578857s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.2438507080078125e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2550506591796875s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.0207064151763916s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.6253204345703125e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 7.3909759521484375e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.9410927295684814s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 8.177757263183594e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2589125633239746s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.961822509765625e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.239776611328125e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 3.9472341537475586s
Availability | SPARQL endpoint availability check for Newsweek took 4.0531158447265625e-05s
Availability | VoID file availability check for Newsweek took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Newsweek took 0.2792017459869385s
Reputation | Calculation of the PageRank for Newsweek took 0.021342039108276367s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.266334533691406e-05s
Believability | Calculation of trust value for Newsweek took 7.867813110351562e-06s
INFO | --- Analysis for newsweek took 2.9070587158203125s
Availability | SPARQL endpoint availability check for neXtProt took 1.521087646484375s
Availability | VoID file availability check for neXtProt took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2763791084289551s
Reputation | Calculation of the PageRank for neXtProt took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.933906555175781e-05s
Believability | Calculation of trust value for neXtProt took 9.059906005859375e-06s
INFO | --- Analysis for nextprot took 4.5035014152526855s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.291534423828125e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2661614418029785s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02109527587890625s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00011920928955078125s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for nextweb-gnoss took 4.71320915222168s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.267692565917969e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.2691936492919922s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020952939987182617s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.416175842285156e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 5.7220458984375e-06s
INFO | --- Analysis for nhs-jargon took 2.857351779937744s
Availability | SPARQL endpoint availability check for NIT Patna took 4.2438507080078125e-05s
Availability | VoID file availability check for NIT Patna took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.26325321197509766s
Reputation | Calculation of the PageRank for NIT Patna took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0009930133819580078s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 8.440017700195312e-05s
Believability | Calculation of trust value for NIT Patna took 8.344650268554688e-06s
INFO | --- Analysis for NITP took 3.402083158493042s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.1961669921875e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.25679874420166016s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.647804260253906e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 7.62939453125e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.908322811126709s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.28020238876342773s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.62939453125e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.119235515594482s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5724353790283203s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.28113794326782227s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for NLW took 4.209262371063232s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.299612283706665s
Availability | VoID file availability check for Nobel Prizes took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.293895959854126s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 0.00011038780212402344s
Believability | Calculation of trust value for Nobel Prizes took 8.58306884765625e-06s
INFO | --- Analysis for nobelprizes took 8.287333250045776s
Availability | SPARQL endpoint availability check for NoiPA took 0.3011956214904785s
Availability | VoID file availability check for NoiPA took 0.0003688335418701172s
Extra | Recovery of all triples for NoiPA took 108.24599599838257s
Performance | Total latancy measurement for NoiPA took 0.6868720054626465s
Amount of data | Number of triples check for NoiPA took 11.344721555709839s
Interoperability | New terms check for NoiPA took 3.6160638332366943s
Versatility | Languages check for NoiPA took 0.3480045795440674s
Interpretability | Number of blank nodes check for NoiPA took 0.14679336547851562s
Interpretability | RDF structures check for NoiPA took 0.1981194019317627s
Versatility | Serialization formats check for NoiPA took 0.16882038116455078s
Availability | RDF dump link check for NoiPA took 0.17058372497558594s
License | MR license check for NoiPA took 0.8781743049621582s
License | HR license check for NoiPA took 60.221765756607056s
Amount of data | Number of property check for NoiPA took 0.18297100067138672s
Understandability | Number of label check for NoiPA took 0.7780880928039551s
Understandability | URI regex check for NoiPA took 0.7373538017272949s
Understandability | Vocabs check for NoiPA took 0.1502852439880371s
Verifiability | Authors check for NoiPA took 0.15668606758117676s
Verifiability | Publishers check for NoiPA took 0.11870384216308594s
Performance | Throughput check for NoiPA took 10.49092984199524s
Amount of data | Check the number of entities for NoiPA took 7.367134094238281e-05s
Verifiability | Contribs. check for NoiPA took 0.12216925621032715s
Interlinking | sameAs chians check for NoiPA took 0.12502264976501465s
Interlinking | skos check for NoiPA took 1.8278825283050537s
Interlinking | skos check for NoiPA took 0.125518798828125s
Timeliness | dataset update frequency check for NoiPA took 0.2392895221710205s
Currency | Creation date check for NoiPA took 0.3154172897338867s
Currency | Modification date check for NoiPA took 0.19376444816589355s
Rep.Conc. | URIs length for NoiPA took 62.243016481399536s
Interoperability | New vocabularies check for NoiPA took 1.9073486328125e-05s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.16873693466186523s
Accuracy | Check Functional Property for NoiPA took 0.31772422790527344s
Accuracy | Check Inverse Functional Property for NoiPA took 0.25059986114501953s
Accuracy | Check Empty annotation labels for NoiPA took 24.182279586791992s
Accuracy | Check White space in annotation for NoiPA took 2.228360652923584s
Accuracy | Check Datatype consistency for NoiPA took 1.9887490272521973s
Consistency | Disjoint class check for NoiPA took 0.20369458198547363s
Consistency | Check Misplaced properties for NoiPA took 18.643123865127563s
Consistency | Misplaced classes for NoiPA took 6.209940433502197s
Consistency | Check Ontology hijacking for NoiPA took 34.44066071510315s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.5763218402862549s
Consistency | Check Invalid usage of undefined properties for NoiPA took 19.83821964263916s
Conciseness | Check Extensional conciseness for NoiPA took 2.20217227935791s
Conciseness | Check Intensional conciseness for NoiPA took 0.16042804718017578s
Security | Sign check for NoiPA took 0.15980863571166992s
Availability | Check URIs Dereferenciability for NoiPA took 12.58897852897644s
Completeness | Calculation of interlinking completeness for NoiPA took 0.5468571186065674s
Reputation | Calculation of the PageRank for NoiPA took 0.021007061004638672s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.1948089599609375e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.9073486328125e-06s
Believability | Calculation of trust value for NoiPA took 7.3909759521484375e-06s
INFO | --- Analysis for NoiPA took 593.7169542312622s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.0989603996276855s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.827707052230835s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.465217590332031e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.3909759521484375e-06s
INFO | --- Analysis for nom took 24.59656858444214s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 34.08178234100342s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008025169372558594s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.6731975078582764s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.02127361297607422s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.130073547363281e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.9604644775390625e-06s
INFO | --- Analysis for nomenclator-asturias took 187.7838761806488s
Availability | SPARQL endpoint availability check for nomisma took 4.2438507080078125e-05s
Availability | VoID file availability check for nomisma took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for nomisma took 0.26915860176086426s
Reputation | Calculation of the PageRank for nomisma took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for nomisma took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for nomisma took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for nomisma took 2.9087066650390625e-05s
Believability | Calculation of trust value for nomisma took 8.344650268554688e-06s
INFO | --- Analysis for nomisma took 4.711545467376709s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.42028307914733887s
Availability | VoID file availability check for Nomisma.org  took 0.0005118846893310547s
Extra | Recovery of all triples for Nomisma.org  took 1122.3303985595703s
Performance | Total latancy measurement for Nomisma.org  took 1.7858819961547852s
Amount of data | Number of triples check for Nomisma.org  took 43.19184422492981s
Interoperability | New terms check for Nomisma.org  took 7.745853900909424s
Versatility | Languages check for Nomisma.org  took 122.89777278900146s
Interpretability | Number of blank nodes check for Nomisma.org  took 37.50876188278198s
Security | Check HTTPS for Nomisma.org  took 0.8228332996368408s
Interpretability | RDF structures check for Nomisma.org  took 0.39176368713378906s
Versatility | Serialization formats check for Nomisma.org  took 0.37389349937438965s
Availability | RDF dump link check for Nomisma.org  took 996.4489464759827s
License | MR license check for Nomisma.org  took 1.913482904434204s
License | HR license check for Nomisma.org  took 55.816935300827026s
Amount of data | Number of property check for Nomisma.org  took 0.3976624011993408s
Understandability | Number of label check for Nomisma.org  took 7.3432512283325195s
Understandability | URI regex check for Nomisma.org  took 0.7365634441375732s
Understandability | Vocabs check for Nomisma.org  took 0.3486361503601074s
Verifiability | Authors check for Nomisma.org  took 0.3654806613922119s
Verifiability | Publishers check for Nomisma.org  took 0.5167450904846191s
Performance | Throughput check for Nomisma.org  took 14.193009376525879s
Amount of data | Check the number of entities for Nomisma.org  took 62.296013832092285s
Verifiability | Contribs. check for Nomisma.org  took 0.41271448135375977s
Interlinking | sameAs chians check for Nomisma.org  took 0.3886373043060303s
Interlinking | skos check for Nomisma.org  took 1.123563289642334s
Interlinking | skos check for Nomisma.org  took 0.5286221504211426s
Timeliness | dataset update frequency check for Nomisma.org  took 0.33022618293762207s
Currency | Creation date check for Nomisma.org  took 0.7288997173309326s
Currency | Modification date check for Nomisma.org  took 0.5662362575531006s
Rep.Conc. | URIs length for Nomisma.org  took 859.9682767391205s
Interoperability | New vocabularies check for Nomisma.org  took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.35961413383483887s
Accuracy | Check Functional Property for Nomisma.org  took 0.3689002990722656s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3326241970062256s
Accuracy | Check Empty annotation labels for Nomisma.org  took 350.18482089042664s
Accuracy | Check White space in annotation for Nomisma.org  took 2.8044865131378174s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.44003701210022s
Consistency | Disjoint class check for Nomisma.org  took 0.38771629333496094s
Consistency | Check Misplaced properties for Nomisma.org  took 29.51846408843994s
Consistency | Check Ontology hijacking for Nomisma.org  took 385.5284173488617s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 1.854907512664795s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 27.251596689224243s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.8194973468780518s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.4143214225769043s
Security | Sign check for Nomisma.org  took 0.44446325302124023s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1861.9634425640106s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.616222858428955s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.022447586059570312s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 2.384185791015625e-06s
Believability | Calculation of trust value for Nomisma.org  took 8.58306884765625e-06s
INFO | --- Analysis for nomisma_org took 10145.074528932571s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.8547806739807129s
Availability | VoID file availability check for Curriculum Vitae took 0.00024580955505371094s
Extra | Recovery of all triples for Curriculum Vitae took 0.4539046287536621s
Performance | Total latancy measurement for Curriculum Vitae took 1.2560226917266846s
Amount of data | Number of triples check for Curriculum Vitae took 0.261214017868042s
Interoperability | New terms check for Curriculum Vitae took 1.5514447689056396s
Versatility | Languages check for Curriculum Vitae took 0.24062705039978027s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.22171568870544434s
Interpretability | RDF structures check for Curriculum Vitae took 0.26613926887512207s
Versatility | Serialization formats check for Curriculum Vitae took 0.24214696884155273s
Availability | RDF dump link check for Curriculum Vitae took 0.23760318756103516s
License | MR license check for Curriculum Vitae took 0.27703237533569336s
License | HR license check for Curriculum Vitae took 0.14559364318847656s
Amount of data | Number of property check for Curriculum Vitae took 0.2705998420715332s
Understandability | Number of label check for Curriculum Vitae took 0.14642047882080078s
Understandability | URI regex check for Curriculum Vitae took 0.2274787425994873s
Understandability | Vocabs check for Curriculum Vitae took 0.11821174621582031s
Verifiability | Authors check for Curriculum Vitae took 0.12465953826904297s
Verifiability | Publishers check for Curriculum Vitae took 0.10441708564758301s
Amount of data | Check the number of entities for Curriculum Vitae took 6.842613220214844e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.21256566047668457s
Interlinking | sameAs chians check for Curriculum Vitae took 0.13225507736206055s
Interlinking | skos check for Curriculum Vitae took 0.2196056842803955s
Interlinking | skos check for Curriculum Vitae took 0.13867902755737305s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.11794543266296387s
Currency | Creation date check for Curriculum Vitae took 0.36567020416259766s
Currency | Modification date check for Curriculum Vitae took 0.43444347381591797s
Rep.Conc. | URIs length for Curriculum Vitae took 0.6669492721557617s
Interoperability | New vocabularies check for Curriculum Vitae took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.2366633415222168s
Accuracy | Check Functional Property for Curriculum Vitae took 0.24421191215515137s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.23475909233093262s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.12944364547729492s
Accuracy | Check White space in annotation for Curriculum Vitae took 9.274482727050781e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.003294229507446289s
Consistency | Disjoint class check for Curriculum Vitae took 0.11866116523742676s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.3503727912902832s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.5649046897888184s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.470747947692871s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.719217300415039s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0013699531555175781s
Security | Sign check for Curriculum Vitae took 0.12615680694580078s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 20.852569580078125s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.26727795600891113s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.02118849754333496s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.170967102050781e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.430511474609375e-06s
Believability | Calculation of trust value for Curriculum Vitae took 9.059906005859375e-06s
INFO | --- Analysis for Nordine_Bittich took 55.86636829376221s
Availability | SPARQL endpoint availability check for NorPark took 0.5294179916381836s
Availability | VoID file availability check for NorPark took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for NorPark took 0.25623106956481934s
Reputation | Calculation of the PageRank for NorPark took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.3392181396484375e-05s
Believability | Calculation of trust value for NorPark took 8.106231689453125e-06s
INFO | --- Analysis for norpark took 3.5481367111206055s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.02321934700012207s
Availability | VoID file availability check for Parking Dataset took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2527649402618408s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.38690185546875e-05s
Believability | Calculation of trust value for Parking Dataset took 7.62939453125e-06s
INFO | --- Analysis for norpark2 took 3.2604846954345703s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.5990884304046631s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.00028252601623535156s
Extra | Recovery of all triples for Norway fishery stocks dataset took 113.04231333732605s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9607372283935547s
Amount of data | Number of triples check for Norway fishery stocks dataset took 7.786150217056274s
Interoperability | New terms check for Norway fishery stocks dataset took 14.265110492706299s
Versatility | Languages check for Norway fishery stocks dataset took 300.2043077945709s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 3.1720330715179443s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.2620246410369873s
Versatility | Serialization formats check for Norway fishery stocks dataset took 11.647510766983032s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.3113517761230469s
License | MR license check for Norway fishery stocks dataset took 0.6440587043762207s
License | HR license check for Norway fishery stocks dataset took 300.2212173938751s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.3276045322418213s
Understandability | Number of label check for Norway fishery stocks dataset took 2.308095693588257s
Understandability | URI regex check for Norway fishery stocks dataset took 0.6931602954864502s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.3889946937561035s
Verifiability | Authors check for Norway fishery stocks dataset took 0.20136356353759766s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2545130252838135s
Performance | Throughput check for Norway fishery stocks dataset took 11.504307508468628s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 7.343292236328125e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.19284772872924805s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.19583559036254883s
Interlinking | skos check for Norway fishery stocks dataset took 0.45162320137023926s
Interlinking | skos check for Norway fishery stocks dataset took 0.4432358741760254s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 6.049716949462891s
Currency | Creation date check for Norway fishery stocks dataset took 0.5022432804107666s
Currency | Modification date check for Norway fishery stocks dataset took 0.2256331443786621s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 148.43566012382507s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.21734333038330078s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.33106279373168945s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.2513580322265625s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 40.45197248458862s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.7208411693573s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.6327950954437256s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.19385957717895508s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 81.14131164550781s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.437456130981445s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 35.63406300544739s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.2356007099151611s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 86.60599899291992s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7435524463653564s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5128147602081299s
Security | Sign check for Norway fishery stocks dataset took 0.8624057769775391s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 10.14621090888977s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 1.275036096572876s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.021074295043945312s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.24249267578125e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 7.3909759521484375e-06s
INFO | --- Analysis for Norway_Fishery_ took 2259.699868440628s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.43633532524108887s
Availability | VoID file availability check for Norwegian geo-divisions took 0.00034880638122558594s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.7001385688781738s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0010075569152832031s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.841255187988281e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 7.152557373046875e-06s
INFO | --- Analysis for norwegian-geo-divisions took 8.637192010879517s
Availability | SPARQL endpoint availability check for NorwegianSoE took 5.14984130859375e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.6997148990631104s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.02119159698486328s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.218650817871094e-05s
Believability | Calculation of trust value for NorwegianSoE took 8.344650268554688e-06s
INFO | --- Analysis for norwegiansoe took 3.668646812438965s
Availability | SPARQL endpoint availability check for NITP took 4.267692565917969e-05s
Availability | VoID file availability check for NITP took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for NITP took 0.237168550491333s
Reputation | Calculation of the PageRank for NITP took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for NITP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NITP took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for NITP took 6.961822509765625e-05s
Believability | Calculation of trust value for NITP took 7.3909759521484375e-06s
INFO | --- Analysis for notIdentifier took 3.7414958477020264s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.1961669921875e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.23228979110717773s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.933906555175781e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 7.3909759521484375e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.6285667419433594s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.029273986816406e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.24875545501708984s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.86102294921875e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 6.67572021484375e-06s
INFO | --- Analysis for npg took 2.902012348175049s
Availability | SPARQL endpoint availability check for NPM took 4.3392181396484375e-05s
Availability | VoID file availability check for NPM took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for NPM took 0.24893641471862793s
Reputation | Calculation of the PageRank for NPM took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for NPM took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007977485656738281s
Interlinking | Calculation of Clustering coefficient for NPM took 3.4332275390625e-05s
Believability | Calculation of trust value for NPM took 1.1920928955078125e-05s
INFO | --- Analysis for npm took 3.2248291969299316s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.06342601776123047s
Availability | VoID file availability check for NTNU special collections took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.25037407875061035s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.555152893066406e-05s
Believability | Calculation of trust value for NTNU special collections took 6.9141387939453125e-06s
INFO | --- Analysis for ntnusc took 5.748284339904785s
Availability | SPARQL endpoint availability check for links took 4.3392181396484375e-05s
Availability | VoID file availability check for links took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for links took 0.2647361755371094s
Reputation | Calculation of the PageRank for links took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for links took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for links took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for links took 1.1920928955078125e-05s
Believability | Calculation of trust value for links took 8.58306884765625e-06s
INFO | --- Analysis for nugmyanmar took 2.306929588317871s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.3392181396484375e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2561063766479492s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.751319885253906e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 5.9604644775390625e-06s
INFO | --- Analysis for nuts-geovocab took 2.3585221767425537s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.4697709083557129s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.261716365814209s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.747245788574219e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 7.867813110351562e-06s
INFO | --- Analysis for nvd took 4.244430303573608s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.8950481414794922s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.28560376167297363s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.021148204803466797s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.678436279296875e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 6.9141387939453125e-06s
INFO | --- Analysis for nvs took 8.233570575714111s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.3392181396484375e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.27123236656188965s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.021434307098388672s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00019216537475585938s
Believability | Calculation of trust value for New York Times - Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.3868207931518555s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.4345855712890625e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.23854756355285645s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.022178173065185547s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0010411739349365234s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.600120544433594e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 7.62939453125e-06s
INFO | --- Analysis for o-anc took 2.907432794570923s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.220008850097656e-05s
Availability | VoID file availability check for OANetzwerk took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.24598956108093262s
Reputation | Calculation of the PageRank for OANetzwerk took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 2.956390380859375e-05s
Believability | Calculation of trust value for OANetzwerk took 1.3113021850585938e-05s
INFO | --- Analysis for oanetzwerk took 2.917376756668091s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.291534423828125e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.2558865547180176s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.1948089599609375e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 8.106231689453125e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.919942617416382s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 1.6579060554504395s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0007162094116210938s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 2.1203181743621826s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.7067854404449463s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 4.333484888076782s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7736425399780273s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.37353992462158s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 3.558349609375s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.6161031723022461s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.47165489196777344s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5471682548522949s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.5110671520233154s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.5080764293670654s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.33914113044739s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 4.46946907043457s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.8423326015472412s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.6776320934295654s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.48038291931152344s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.3190317153930664s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3313138484954834s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.763709545135498s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.224082946777344e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.3412466049194336s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.312441349029541s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.31932687759399414s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3126382827758789s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.45246124267578125s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.8117225170135498s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.33449435234069824s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 17.45760202407837s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 1.6636137962341309s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.36017394065856934s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.3317406177520752s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.9883391857147217s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.02398061752319336s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.02865314483642578s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 3.745274543762207s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 14.419480085372925s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.4420332908630371s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.0957188606262207s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.1907122135162354s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.950891256332397s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03190040588378906s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.3619809150695801s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3570747375488281s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 11.296170234680176s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.37801337242126465s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.021745681762695312s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.00103759765625s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00011491775512695312s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 2.384185791015625e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 8.821487426757812e-06s
INFO | --- Analysis for ocd took 473.7986092567444s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 7.963180541992188e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.27855801582336426s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020880699157714844s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.7670135498046875e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-borehole took 4.0824971199035645s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.3624866008758545s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.271406888961792s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020855188369750977s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 9.322166442871094e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-codices took 7.757191181182861s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.2118806838989258s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2554903030395508s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 5.915760278701782s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.1911537647247314s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0008847713470458984s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.26804351806640625s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.337860107421875e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-forams took 5.613783121109009s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.1673858165740967s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.254030704498291s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.023095130920410156s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0012021064758300781s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 4.649162292480469e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-janus took 5.7273476123809814s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 10.921365976333618s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.28537440299987793s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.409385681152344e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-janusamp took 15.904606103897095s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1277265548706055s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2571756839752197s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.86102294921875e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-ldeo took 5.6076905727386475s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 7.081031799316406e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.27773165702819824s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.000865936279296875s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.9604644775390625e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.1682510375976562e-05s
INFO | --- Analysis for oclc-fast took 7.822684288024902s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.220008850097656e-05s
Availability | VoID file availability check for Open Data Communities took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2820110321044922s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Data Communities took 7.62939453125e-06s
INFO | --- Analysis for odc took 2.909625291824341s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.267692565917969e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.25795888900756836s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.0067901611328125e-06s
INFO | --- Analysis for odc-imd-environment-score took 3.3152987957000732s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.124641418457031e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2836418151855469s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.86102294921875e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 1.239776611328125e-05s
INFO | --- Analysis for odc-imd-rank-2007 took 2.9472436904907227s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.2770998477935791s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2673063278198242s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.5762786865234375e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 6.4373016357421875e-06s
INFO | --- Analysis for odc-lsoa took 3.6022424697875977s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.124641418457031e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.24033522605895996s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.021345853805541992s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0008296966552734375s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.4332275390625e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 7.3909759521484375e-06s
INFO | --- Analysis for odc-population-2005 took 2.794882297515869s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.1484832763671875e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.26572465896606445s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 8.58306884765625e-06s
INFO | --- Analysis for ods took 2.8636012077331543s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.8481688499450684s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.26619482040405273s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.393692016601562e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for oecd-linked-data took 3.2324366569519043s
Availability | SPARQL endpoint availability check for Offener Haushalt took 3.933906555175781e-05s
Availability | VoID file availability check for Offener Haushalt took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.2565944194793701s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 2.86102294921875e-05s
Believability | Calculation of trust value for Offener Haushalt took 7.62939453125e-06s
INFO | --- Analysis for offener-haushalt took 2.8743066787719727s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.146903038024902s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.26805543899536133s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.172325134277344e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 6.4373016357421875e-06s
INFO | --- Analysis for ogolod took 102.65143752098083s
Availability | SPARQL endpoint availability check for OLAC Metadata took 6.67572021484375e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.2852168083190918s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.933906555175781e-05s
Believability | Calculation of trust value for OLAC Metadata took 6.67572021484375e-06s
INFO | --- Analysis for olac took 23.10456347465515s
Availability | SPARQL endpoint availability check for OLiA took 4.100799560546875e-05s
Availability | VoID file availability check for OLiA took 0.0008187294006347656s
Completeness | Calculation of interlinking completeness for OLiA took 0.2778475284576416s
Reputation | Calculation of the PageRank for OLiA took 0.021044015884399414s
Interlinking | Calculation of Degree of Connection for OLiA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.000125885009765625s
Believability | Calculation of trust value for OLiA took 8.106231689453125e-06s
INFO | --- Analysis for olia took 12.324912786483765s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.363059997558594e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007805824279785156s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.7111039161682129s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02098369598388672s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.291534423828125e-05s
Believability | Calculation of trust value for OLiA Discourse took 7.867813110351562e-06s
INFO | --- Analysis for olia-discourse took 7.827200412750244s
Availability | SPARQL endpoint availability check for Open Land Use took 0.2834935188293457s
Availability | VoID file availability check for Open Land Use took 0.0002834796905517578s
Extra | Recovery of all triples for Open Land Use took 112.15836787223816s
Performance | Total latancy measurement for Open Land Use took 0.9523448944091797s
Amount of data | Number of triples check for Open Land Use took 8.815475940704346s
Interoperability | New terms check for Open Land Use took 14.54154348373413s
Versatility | Languages check for Open Land Use took 300.2457399368286s
Interpretability | Number of blank nodes check for Open Land Use took 3.2765111923217773s
Interpretability | RDF structures check for Open Land Use took 0.2375786304473877s
Versatility | Serialization formats check for Open Land Use took 10.129915237426758s
Availability | RDF dump link check for Open Land Use took 0.24848318099975586s
License | MR license check for Open Land Use took 0.5338382720947266s
License | HR license check for Open Land Use took 300.2043311595917s
Amount of data | Number of property check for Open Land Use took 0.2692432403564453s
Understandability | Number of label check for Open Land Use took 2.503865957260132s
Understandability | URI regex check for Open Land Use took 0.6132767200469971s
Understandability | Vocabs check for Open Land Use took 0.3825106620788574s
Verifiability | Authors check for Open Land Use took 0.19264602661132812s
Verifiability | Publishers check for Open Land Use took 0.24107694625854492s
Performance | Throughput check for Open Land Use took 10.782203435897827s
Amount of data | Check the number of entities for Open Land Use took 7.510185241699219e-05s
Verifiability | Contribs. check for Open Land Use took 0.1768035888671875s
Interlinking | sameAs chians check for Open Land Use took 0.18415141105651855s
Interlinking | skos check for Open Land Use took 0.44338202476501465s
Interlinking | skos check for Open Land Use took 0.4294726848602295s
Timeliness | dataset update frequency check for Open Land Use took 5.271032810211182s
Currency | Creation date check for Open Land Use took 0.46027517318725586s
Currency | Modification date check for Open Land Use took 0.21262097358703613s
Rep.Conc. | URIs length for Open Land Use took 152.2056496143341s
Interoperability | New vocabularies check for Open Land Use took 1.33514404296875e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.21608662605285645s
Accuracy | Check Functional Property for Open Land Use took 0.3033864498138428s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.31159448623657227s
Accuracy | Check Empty annotation labels for Open Land Use took 40.63452696800232s
Accuracy | Check White space in annotation for Open Land Use took 2.7023096084594727s
Accuracy | Check Datatype consistency for Open Land Use took 2.6199026107788086s
Consistency | Disjoint class check for Open Land Use took 0.18027925491333008s
Consistency | Check Misplaced properties for Open Land Use took 84.93808603286743s
Consistency | Misplaced classes for Open Land Use took 8.511775493621826s
Consistency | Check Ontology hijacking for Open Land Use took 32.85952162742615s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.2308332920074463s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 85.09844613075256s
Conciseness | Check Extensional conciseness for Open Land Use took 2.748931646347046s
Conciseness | Check Intensional conciseness for Open Land Use took 0.6031196117401123s
Security | Sign check for Open Land Use took 0.8538689613342285s
Availability | Check URIs Dereferenciability for Open Land Use took 8.211682319641113s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.5804681777954102s
Reputation | Calculation of the PageRank for Open Land Use took 0.021434783935546875s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0008230209350585938s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Land Use took 7.3909759521484375e-06s
INFO | --- Analysis for OLU took 2228.4648990631104s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.3392181396484375e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.7017879486083984s
Reputation | Calculation of the PageRank for OmegaWiki took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.6716461181640625e-05s
Believability | Calculation of trust value for OmegaWiki took 7.867813110351562e-06s
INFO | --- Analysis for omegawiki took 4.959019899368286s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.7846791744232178s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.24665498733520508s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.021476030349731445s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-als took 3.881293296813965s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.25099658966064453s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.24867844581604004s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-arb took 3.3274972438812256s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.25328755378723145s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2432401180267334s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-bul took 3.2592108249664307s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2309250831604004s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00036334991455078125s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.23702764511108398s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-cow took 2.7309751510620117s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2112717628479004s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0003581047058105469s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.24621272087097168s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-cwn took 3.2761709690093994s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2626039981842041s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.24094820022583008s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-dan took 2.767448902130127s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.2582859992980957s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00036144256591796875s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2452077865600586s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0008625984191894531s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-ell took 2.79338002204895s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.21987628936767578s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2376420497894287s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-eng took 2.7307376861572266s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.22311019897460938s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.24238276481628418s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-fas took 2.743677854537964s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.23164010047912598s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.23873519897460938s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.020670652389526367s
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.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-fin took 2.747162103652954s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.23280072212219238s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.24957656860351562s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.021006345748901367s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-fra took 2.7488551139831543s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.22619152069091797s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.25546741485595703s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02129817008972168s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0010044574737548828s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 5.054473876953125e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-heb took 2.7804365158081055s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.23453140258789062s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.23871135711669922s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-hrv took 2.7987937927246094s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2395639419555664s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2428731918334961s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-isl took 2.7542977333068848s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2331066131591797s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.23890423774719238s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.267692565917969e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-ita took 2.741809844970703s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2334599494934082s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2330467700958252s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-iwn took 2.7256526947021484s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.21322083473205566s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.24355006217956543s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-jpn took 2.741013526916504s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.22279906272888184s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.24136114120483398s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-mcr took 2.692643880844116s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.24648070335388184s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2537999153137207s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0009701251983642578s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 4.4345855712890625e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-msa took 2.7328743934631348s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.22515487670898438s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.24325108528137207s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02113795280456543s
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.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-nld took 2.7165019512176514s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.22968816757202148s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.23938298225402832s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.457069396972656e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-nor took 2.7080841064453125s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.19858741760253906s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.24194550514221191s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-pol took 2.6752116680145264s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.21369338035583496s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.23604226112365723s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-por took 2.7287023067474365s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2230391502380371s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.24362754821777344s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.02135300636291504s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-ron took 2.6860556602478027s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.23284482955932617s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.24134302139282227s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-slk took 2.7646126747131348s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.22191286087036133s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.24535369873046875s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-slv took 2.723234176635742s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.23965215682983398s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2319960594177246s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020764589309692383s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-swe took 2.701786994934082s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.22272682189941406s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2462928295135498s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 5.602836608886719e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-tha took 2.7209384441375732s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.257379531860352s
Availability | VoID file availability check for OntoBeef Domain took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2476804256439209s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.291534423828125e-05s
Believability | Calculation of trust value for OntoBeef Domain took 6.9141387939453125e-06s
INFO | --- Analysis for ontobeef-domain took 29.26925778388977s
Availability | SPARQL endpoint availability check for Ontos News Portal took 5.269050598144531e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.23883295059204102s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.5367431640625e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.3909759521484375e-06s
INFO | --- Analysis for ontos-news-portal took 3.319162130355835s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 7.677078247070312e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.23859524726867676s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.147125244140625e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.152557373046875e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.2422516345977783s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.553794860839844e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.24351811408996582s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.719329833984375e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 7.3909759521484375e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.037631750106812s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.24018430709838867s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 7.867813110351562e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.623218059539795s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.38690185546875e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2408437728881836s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.696846008300781e-05s
Believability | Calculation of trust value for Open Data Euskadi took 6.198883056640625e-06s
INFO | --- Analysis for open-data-euskadi took 7.502782106399536s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.24396347999572754s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.021070003509521484s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010061264038085938s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 8.821487426757812e-06s
INFO | --- Analysis for open-data-risp took 4.101681232452393s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.22531628608703613s
Availability | VoID file availability check for Open Data Thesaurus took 0.0007405281066894531s
Extra | Recovery of all triples for Open Data Thesaurus took 1.3015422821044922s
Performance | Total latancy measurement for Open Data Thesaurus took 0.48800086975097656s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1230313777923584s
Interoperability | New terms check for Open Data Thesaurus took 1.2784967422485352s
Versatility | Languages check for Open Data Thesaurus took 0.1087334156036377s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.12117981910705566s
Security | Check HTTPS for Open Data Thesaurus took 0.2908949851989746s
Interpretability | RDF structures check for Open Data Thesaurus took 0.10459518432617188s
Versatility | Serialization formats check for Open Data Thesaurus took 0.12341427803039551s
Availability | RDF dump link check for Open Data Thesaurus took 1.0562639236450195s
License | MR license check for Open Data Thesaurus took 0.10384082794189453s
License | HR license check for Open Data Thesaurus took 0.08367586135864258s
Amount of data | Number of property check for Open Data Thesaurus took 0.10414433479309082s
Understandability | Number of label check for Open Data Thesaurus took 0.12262749671936035s
Understandability | URI regex check for Open Data Thesaurus took 0.15998053550720215s
Understandability | Vocabs check for Open Data Thesaurus took 0.10342884063720703s
Verifiability | Authors check for Open Data Thesaurus took 0.10371708869934082s
Verifiability | Publishers check for Open Data Thesaurus took 0.10341668128967285s
Performance | Throughput check for Open Data Thesaurus took 10.35867691040039s
Amount of data | Check the number of entities for Open Data Thesaurus took 8.535385131835938e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.12080860137939453s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.12055730819702148s
Interlinking | skos check for Open Data Thesaurus took 0.10663437843322754s
Interlinking | skos check for Open Data Thesaurus took 0.08030867576599121s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.0798182487487793s
Currency | Creation date check for Open Data Thesaurus took 0.1677110195159912s
Currency | Modification date check for Open Data Thesaurus took 0.18668460845947266s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.42745518684387207s
Interoperability | New vocabularies check for Open Data Thesaurus took 8.44879961013794s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.10506892204284668s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.07979369163513184s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.10001206398010254s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1576683521270752s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011322498321533203s
Consistency | Disjoint class check for Open Data Thesaurus took 0.08105945587158203s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.17013859748840332s
Consistency | Misplaced classes for Open Data Thesaurus took 0.08085393905639648s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.3380990028381348s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.267697811126709s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001461505889892578s
Security | Sign check for Open Data Thesaurus took 0.07848286628723145s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.2537364959716797s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.02019476890563965s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0008575916290283203s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 8.69937515258789s
Believability | Calculation of trust value for Open Data Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for open-data-thesaurus took 77.92990136146545s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.291534423828125e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.24220061302185059s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.0210418701171875s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 3.0517578125e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 8.106231689453125e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.6844115257263184s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.267692565917969e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.24548649787902832s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.818771362304688e-05s
Believability | Calculation of trust value for Open Election Data Project took 6.4373016357421875e-06s
INFO | --- Analysis for open-election-data-project took 4.779763698577881s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.745220422744751s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.23923826217651367s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.726119995117188e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 8.344650268554688e-06s
INFO | --- Analysis for open-energy-info-wiki took 10.47714877128601s
Availability | SPARQL endpoint availability check for Open Library took 4.220008850097656e-05s
Availability | VoID file availability check for Open Library took 0.0009403228759765625s
Completeness | Calculation of interlinking completeness for Open Library took 0.24629497528076172s
Reputation | Calculation of the PageRank for Open Library took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for Open Library took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.009506225585938e-05s
Believability | Calculation of trust value for Open Library took 7.3909759521484375e-06s
INFO | --- Analysis for open-library took 10.007938623428345s
Availability | SPARQL endpoint availability check for Open Directory took 4.172325134277344e-05s
Availability | VoID file availability check for Open Directory took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Open Directory took 0.24807500839233398s
Reputation | Calculation of the PageRank for Open Directory took 0.02077627182006836s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.0279159545898438e-05s
Believability | Calculation of trust value for Open Directory took 7.3909759521484375e-06s
INFO | --- Analysis for open_directory took 2.6597254276275635s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.1746823787689209s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0002684593200683594s
Extra | Recovery of all triples for Open Land Use @PSNC took 120.27058124542236s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.8945841789245605s
Amount of data | Number of triples check for Open Land Use @PSNC took 8.161344528198242s
Interoperability | New terms check for Open Land Use @PSNC took 13.449333667755127s
Versatility | Languages check for Open Land Use @PSNC took 300.1826148033142s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 3.5356390476226807s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.2731759548187256s
Versatility | Serialization formats check for Open Land Use @PSNC took 9.338443756103516s
Availability | RDF dump link check for Open Land Use @PSNC took 0.246612548828125s
License | MR license check for Open Land Use @PSNC took 0.6393256187438965s
License | HR license check for Open Land Use @PSNC took 300.1505436897278s
Amount of data | Number of property check for Open Land Use @PSNC took 0.19408559799194336s
Understandability | Number of label check for Open Land Use @PSNC took 3.3042397499084473s
Understandability | URI regex check for Open Land Use @PSNC took 0.6123406887054443s
Understandability | Vocabs check for Open Land Use @PSNC took 0.32099246978759766s
Verifiability | Authors check for Open Land Use @PSNC took 0.1885685920715332s
Verifiability | Publishers check for Open Land Use @PSNC took 0.2430429458618164s
Performance | Throughput check for Open Land Use @PSNC took 10.658554553985596s
Amount of data | Check the number of entities for Open Land Use @PSNC took 6.771087646484375e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.17596817016601562s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.18758463859558105s
Interlinking | skos check for Open Land Use @PSNC took 0.5286307334899902s
Interlinking | skos check for Open Land Use @PSNC took 0.43421483039855957s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 5.2931811809539795s
Currency | Creation date check for Open Land Use @PSNC took 0.4585895538330078s
Currency | Modification date check for Open Land Use @PSNC took 0.2082500457763672s
Rep.Conc. | URIs length for Open Land Use @PSNC took 146.2607123851776s
Interoperability | New vocabularies check for Open Land Use @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.1845231056213379s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.362931489944458s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.3467245101928711s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 42.4836163520813s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.684939384460449s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.59688138961792s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.1829698085784912s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 82.87518453598022s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.509740114212036s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 34.45265746116638s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.2426249980926514s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 87.84088659286499s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.768322229385376s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.6736280918121338s
Security | Sign check for Open Land Use @PSNC took 1.1481869220733643s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.848978757858276s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.9166829586029053s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for Open_Land_Use took 2232.407201528549s
Availability | SPARQL endpoint availability check for flyatlas took 1.6107592582702637s
Availability | VoID file availability check for flyatlas took 0.00038695335388183594s
Completeness | Calculation of interlinking completeness for flyatlas took 0.6757986545562744s
Reputation | Calculation of the PageRank for flyatlas took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.361701965332031e-05s
Believability | Calculation of trust value for flyatlas took 8.106231689453125e-06s
INFO | --- Analysis for openbiomed-flyatlas took 11.640721797943115s
Availability | SPARQL endpoint availability check for OpenCalais took 4.291534423828125e-05s
Availability | VoID file availability check for OpenCalais took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.23953700065612793s
Reputation | Calculation of the PageRank for OpenCalais took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010848045349121094s
Believability | Calculation of trust value for OpenCalais took 8.58306884765625e-06s
INFO | --- Analysis for opencalais took 4.79723334312439s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.315376281738281e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.24248790740966797s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.677078247070312e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 6.9141387939453125e-06s
INFO | --- Analysis for opencorporates took 3.331430435180664s
Availability | SPARQL endpoint availability check for OpenCyc took 4.172325134277344e-05s
Availability | VoID file availability check for OpenCyc took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.23284554481506348s
Reputation | Calculation of the PageRank for OpenCyc took 0.020995140075683594s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010704994201660156s
Believability | Calculation of trust value for OpenCyc took 1.1444091796875e-05s
INFO | --- Analysis for opencyc took 2.1636345386505127s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.24176836013793945s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.4332275390625e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 2.371345043182373s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 5.841255187988281e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.24377226829528809s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.177396535873413s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.23247265815734863s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.2646236419677734s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.23715806007385254s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.1052663326263428s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2406477928161621s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.1882245540618896s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.23984837532043457s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.02099156379699707s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.255871057510376s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.244584321975708s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.2920074462890625s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00010514259338378906s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2403576374053955s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.1331143379211426s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.23454856872558594s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.2224526405334473s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.001180410385131836s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.24255609512329102s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.02107524871826172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.2171790599823s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.24099493026733398s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.021001577377319336s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.2454047203063965s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 5.4836273193359375e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.24032187461853027s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.203075885772705s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.23944783210754395s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02114558219909668s
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.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.2194366455078125s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.23998379707336426s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.022481918334960938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.174076795578003s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.23978352546691895s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02088451385498047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.9591064453125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.209047794342041s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.24245524406433105s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.274301052093506s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0012664794921875s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.24266314506530762s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.021849870681762695s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.059906005859375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.295720338821411s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.22892189025878906s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.2242884635925293s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 7.510185241699219e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.23899483680725098s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020975351333618164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.12959885597229s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.24503302574157715s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.021259546279907227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0009059906005859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.2632040977478027s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.2384936809539795s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.02167654037475586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.2516674995422363s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2373189926147461s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.227970838546753s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.24274468421936035s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007312297821044922s
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 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.229365587234497s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.744529724121094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.23662137985229492s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.206737995147705s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.23917579650878906s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.230557918548584s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 5.5789947509765625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0012366771697998047s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.24164724349975586s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.250168800354004s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.23755407333374023s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.2257401943206787s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.23897171020507812s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020956993103027344s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.2197821140289307s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.24111318588256836s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020983219146728516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.2141640186309814s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.23763585090637207s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.021204471588134766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.1819980144500732s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.23810601234436035s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.2811405658721924s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2425675392150879s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0209195613861084s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.2941460609436035s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.24184513092041016s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.2285118103027344s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.23545289039611816s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02162456512451172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0010361671447753906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.8650970458984375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.1406443119049072s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.24626374244689941s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.02115321159362793s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.15413498878479s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0003943443298339844s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.23610997200012207s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020953655242919922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.887580871582031e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.221874713897705s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0012755393981933594s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.23899340629577637s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02106642723083496s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.2494680881500244s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 7.152557373046875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2357039451599121s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020922183990478516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.1875174045562744s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2429344654083252s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.02229928970336914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0008437633514404297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.258516311645508s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2393960952758789s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.02106618881225586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.2132418155670166s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.23995375633239746s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02161860466003418s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.218527317047119s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0010528564453125s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.24022388458251953s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.2560575008392334s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.23876309394836426s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.196531057357788s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 3.4823150634765625s
Availability | VoID file availability check for Open Data of Ecuador took 0.0003209114074707031s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2375943660736084s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.021234750747680664s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.988380432128906e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 8.821487426757812e-06s
INFO | --- Analysis for opendataec took 7.743226051330566s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.23728585243225098s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020992279052734375s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.344650268554688e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.2592058181762695s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.267692565917969e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0012252330780029297s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.23787665367126465s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.021512746810913086s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.2968153953552246s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2434229850769043s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.02090620994567871s
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.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.869899034500122s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 0.00013136863708496094s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.24260234832763672s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.021015167236328125s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.864206314086914s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 5.698204040527344e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.2379150390625s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020711898803710938s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.824164867401123s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.220008850097656e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2428879737854004s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.852814197540283s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.315376281738281e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.24432802200317383s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.8731608390808105s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.24173641204833984s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.022515058517456055s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.001102447509765625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 5.125999450683594e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.8479433059692383s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.23946475982666016s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020922183990478516s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.1172945499420166s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.503471851348877s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.23934102058410645s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0008633136749267578s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.600120544433594e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 7.867813110351562e-06s
INFO | --- Analysis for openlink-lod-cache took 62.78173232078552s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.267692565917969e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.2378699779510498s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.34600830078125e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 7.62939453125e-06s
INFO | --- Analysis for openlinksw-dataspaces took 2.284874439239502s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.1961669921875e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.23990511894226074s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.322166442871094e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.7220458984375e-06s
INFO | --- Analysis for openlylocal took 8.144588708877563s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.736936092376709s
Availability | VoID file availability check for OpenMobileNetwork took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2400059700012207s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.486343383789062e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 8.106231689453125e-06s
INFO | --- Analysis for openmobilenetwork took 3.3702473640441895s
Availability | SPARQL endpoint availability check for OpenTox took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenTox took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for OpenTox took 0.2391800880432129s
Reputation | Calculation of the PageRank for OpenTox took 0.022182941436767578s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenTox took 7.62939453125e-06s
INFO | --- Analysis for opentox took 2.6222054958343506s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.23923897743225098s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.170967102050781e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 8.344650268554688e-06s
INFO | --- Analysis for openuplabs took 2.6114134788513184s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 8.535385131835938e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.23502731323242188s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 3.24249267578125e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 7.3909759521484375e-06s
INFO | --- Analysis for opus took 2.5726048946380615s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.100799560546875e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.24290156364440918s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.647804260253906e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 8.58306884765625e-06s
INFO | --- Analysis for orcid took 2.564242362976074s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9519989490509033s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2435905933380127s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.021178007125854492s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0009450912475585938s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.00010967254638671875s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 4.949628829956055s
Availability | SPARQL endpoint availability check for oreilly took 4.291534423828125e-05s
Availability | VoID file availability check for oreilly took 0.000377655029296875s
Completeness | Calculation of interlinking completeness for oreilly took 0.23267459869384766s
Reputation | Calculation of the PageRank for oreilly took 0.021790027618408203s
Interlinking | Calculation of Degree of Connection for oreilly took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0008945465087890625s
Interlinking | Calculation of Clustering coefficient for oreilly took 6.842613220214844e-05s
Believability | Calculation of trust value for oreilly took 9.5367431640625e-06s
INFO | --- Analysis for oreilly took 4.334309816360474s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 6.515359878540039s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.23100829124450684s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020946502685546875s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.5762786865234375e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 7.152557373046875e-06s
INFO | --- Analysis for Organchem-Data took 10.68335223197937s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.04333090782165527s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.23113560676574707s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.961822509765625e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for organic-edunet took 8.644134044647217s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.3919363021850586s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.00044465065002441406s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 11.02967119216919s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.754936933517456s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.16929054260253906s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.5277464389801025s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 6.737169504165649s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.1458263397216797s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.20565485954284668s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.13900256156921387s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.14057159423828125s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.1699836254119873s
License | HR license check for Open Research Knowledge Graph (ORKG) took 4.930615663528442s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.15582966804504395s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.1806635856628418s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.26782894134521484s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.14083194732666016s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.1416785717010498s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.1859734058380127s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.486515045166016s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 6.890296936035156e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.14710354804992676s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.1260082721710205s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16373658180236816s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.14525103569030762s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.15657806396484375s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3684091567993164s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.4273245334625244s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 7.40810227394104s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.16235017776489258s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.2782914638519287s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.27010202407836914s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 6.044145584106445s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.2960491180419922s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.27245402336120605s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.17935872077941895s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.4024512767791748s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.8909697532653809s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 4.754391431808472s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.2300965785980225s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 1.9830646514892578s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2895638942718506s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.1297595500946045s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.13992929458618164s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 1930.0846326351166s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 1.4622321128845215s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021773099899291992s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 6.699562072753906e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 7.62939453125e-06s
INFO | --- Analysis for orkg took 2193.5512113571167s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.9712069034576416s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.7002520561218262s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.021173954010009766s
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.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.726119995117188e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 8.58306884765625e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 30.097702980041504s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.4816601276397705s
Availability | VoID file availability check for OSM Semantic Network took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.24465298652648926s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.647804260253906e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.867813110351562e-06s
INFO | --- Analysis for osm-semantic-network took 8.564022064208984s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.44935131072998047s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0002741813659667969s
Extra | Recovery of all triples for Open Transport Map @PSNC took 102.81629872322083s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.8818275928497314s
Amount of data | Number of triples check for Open Transport Map @PSNC took 8.600863456726074s
Interoperability | New terms check for Open Transport Map @PSNC took 13.64302682876587s
Versatility | Languages check for Open Transport Map @PSNC took 300.2393751144409s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 3.0284273624420166s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.24794507026672363s
Versatility | Serialization formats check for Open Transport Map @PSNC took 11.31635856628418s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.30452585220336914s
License | MR license check for Open Transport Map @PSNC took 0.6893830299377441s
License | HR license check for Open Transport Map @PSNC took 300.1650393009186s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.3713493347167969s
Understandability | Number of label check for Open Transport Map @PSNC took 2.7096505165100098s
Understandability | URI regex check for Open Transport Map @PSNC took 0.8569371700286865s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.44715261459350586s
Verifiability | Authors check for Open Transport Map @PSNC took 0.18940258026123047s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.24628114700317383s
Performance | Throughput check for Open Transport Map @PSNC took 10.751519680023193s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 0.00010371208190917969s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.1840357780456543s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.18616557121276855s
Interlinking | skos check for Open Transport Map @PSNC took 0.4686148166656494s
Interlinking | skos check for Open Transport Map @PSNC took 0.428943395614624s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 6.834125995635986s
Currency | Creation date check for Open Transport Map @PSNC took 0.461057186126709s
Currency | Modification date check for Open Transport Map @PSNC took 0.2101733684539795s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 151.12160778045654s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.1808924674987793s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.34269165992736816s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.3410212993621826s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 37.961087703704834s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.7015936374664307s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.595081090927124s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.19133806228637695s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 86.90086245536804s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.337019443511963s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 32.90678906440735s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.2246344089508057s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 84.00310826301575s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.772317409515381s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.5939524173736572s
Security | Sign check for Open Transport Map @PSNC took 0.9879999160766602s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 10.206219673156738s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 1.281498670578003s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.021032094955444336s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.3855438232421875e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 1.1444091796875e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for OTM took 2229.8851969242096s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.23768043518066406s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.02095937728881836s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 4.863739013671875e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.62939453125e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 5.853869199752808s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 7.033348083496094e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.24341917037963867s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.021030664443969727s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007338523864746094s
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 1.3589859008789062e-05s
INFO | --- Analysis for ox-ac-uk-catalogue took 3.5270020961761475s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.696846008300781e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.2479114532470703s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02141857147216797s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0009765625s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.409385681152344e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 3.103024959564209s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.2358994483947754s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 6.4373016357421875e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 2.633735418319702s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.076957702636719e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.2404923439025879s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.021063566207885742s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 3.361701965332031e-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 2.619473934173584s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.1484832763671875e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.23727631568908691s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.147125244140625e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.6000516414642334s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 5.316734313964844e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.22880077362060547s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.02114129066467285s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.170967102050781e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 8.58306884765625e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.5466363430023193s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.38690185546875e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.23357510566711426s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 3.0517578125e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 3.0040740966796875e-05s
INFO | --- Analysis for oxpoints took 2.5714094638824463s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.7018208503723145s
Availability | VoID file availability check for Pali English Lexicon took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.2414243221282959s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020669221878051758s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.0040740966796875e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.152557373046875e-06s
INFO | --- Analysis for pali-english-lexicon took 6.415729284286499s
Availability | SPARQL endpoint availability check for PanLex took 0.33397626876831055s
Availability | VoID file availability check for PanLex took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for PanLex took 0.23824048042297363s
Reputation | Calculation of the PageRank for PanLex took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.414817810058594e-05s
Believability | Calculation of trust value for PanLex took 1.5974044799804688e-05s
INFO | --- Analysis for panlex took 2.5181591510772705s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.482269287109375e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0004019737243652344s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.2428443431854248s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020423412322998047s
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.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.62396240234375e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 7.152557373046875e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.639017343521118s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.10705184936523438s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2423539161682129s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.839897155761719e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.3296031951904297s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.124641418457031e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.23791933059692383s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.03185248374938965s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0012607574462890625s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 5.364418029785156e-05s
Believability | Calculation of trust value for PDEV-Lemon took 7.867813110351562e-06s
INFO | --- Analysis for pdev-lemon took 11.806437015533447s
Availability | SPARQL endpoint availability check for pdevlemon took 4.1961669921875e-05s
Availability | VoID file availability check for pdevlemon took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.24482131004333496s
Reputation | Calculation of the PageRank for pdevlemon took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.0994415283203125e-05s
Believability | Calculation of trust value for pdevlemon took 7.3909759521484375e-06s
INFO | --- Analysis for pdevlemon took 2.883885145187378s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.3392181396484375e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0007929801940917969s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.24457073211669922s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.797645568847656e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 7.62939453125e-06s
INFO | --- Analysis for periodo took 18.637842893600464s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.3392181396484375e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2375485897064209s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00039315223693847656s
Believability | Calculation of trust value for Personal_Homepages took 7.62939453125e-06s
INFO | --- Analysis for personal-homepages took 2.1440796852111816s
Availability | SPARQL endpoint availability check for Ontology of University People took 5.626678466796875e-05s
Availability | VoID file availability check for Ontology of University People took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2382495403289795s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.765655517578125e-05s
Believability | Calculation of trust value for Ontology of University People took 1.2159347534179688e-05s
INFO | --- Analysis for PersonOnto took 2.1497933864593506s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.044935464859009s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2402658462524414s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1205673217773438e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.62939453125e-06s
INFO | --- Analysis for PFKHS took 11.827300548553467s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.757525205612183s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2433626651763916s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2636184692382812e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.049041748046875e-05s
INFO | --- Analysis for PFRPPH took 10.853382349014282s
Availability | SPARQL endpoint availability check for PGxLOD took 0.36948537826538086s
Availability | VoID file availability check for PGxLOD took 0.0006041526794433594s
Extra | Recovery of all triples for PGxLOD took 2.118192434310913s
Performance | Total latancy measurement for PGxLOD took 0.7497875690460205s
Amount of data | Number of triples check for PGxLOD took 0.8896694183349609s
Interoperability | New terms check for PGxLOD took 1.8624448776245117s
Versatility | Languages check for PGxLOD took 60.224814891815186s
Interpretability | Number of blank nodes check for PGxLOD took 1.5722506046295166s
Interpretability | RDF structures check for PGxLOD took 0.5529146194458008s
Versatility | Serialization formats check for PGxLOD took 0.3655357360839844s
Availability | RDF dump link check for PGxLOD took 48.34640550613403s
License | MR license check for PGxLOD took 0.5980813503265381s
License | HR license check for PGxLOD took 61.919429779052734s
Amount of data | Number of property check for PGxLOD took 0.15929937362670898s
Understandability | Number of label check for PGxLOD took 1.839935302734375s
Understandability | URI regex check for PGxLOD took 0.4187169075012207s
Understandability | Vocabs check for PGxLOD took 0.3565022945404053s
Verifiability | Authors check for PGxLOD took 0.19572186470031738s
Verifiability | Publishers check for PGxLOD took 0.31353306770324707s
Performance | Throughput check for PGxLOD took 10.413095235824585s
Amount of data | Check the number of entities for PGxLOD took 0.12165093421936035s
Verifiability | Contribs. check for PGxLOD took 0.15410494804382324s
Interlinking | sameAs chians check for PGxLOD took 0.2513620853424072s
Interlinking | skos check for PGxLOD took 1.5344648361206055s
Interlinking | skos check for PGxLOD took 0.1815807819366455s
Timeliness | dataset update frequency check for PGxLOD took 0.346621036529541s
Currency | Creation date check for PGxLOD took 0.4992976188659668s
Currency | Modification date check for PGxLOD took 0.32352399826049805s
Rep.Conc. | URIs length for PGxLOD took 6.728738069534302s
Interoperability | New vocabularies check for PGxLOD took 23.24599051475525s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.15605521202087402s
Accuracy | Check Functional Property for PGxLOD took 0.17621326446533203s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.17775464057922363s
Accuracy | Check Empty annotation labels for PGxLOD took 1.0306923389434814s
Accuracy | Check White space in annotation for PGxLOD took 0.03700613975524902s
Accuracy | Check Datatype consistency for PGxLOD took 0.02840256690979004s
Consistency | Disjoint class check for PGxLOD took 0.2925281524658203s
Consistency | Check Misplaced properties for PGxLOD took 6.545895338058472s
Consistency | Misplaced classes for PGxLOD took 0.28148889541625977s
Consistency | Check Ontology hijacking for PGxLOD took 1.9330806732177734s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.1735785007476807s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 6.963988780975342s
Conciseness | Check Extensional conciseness for PGxLOD took 0.031941890716552734s
Conciseness | Check Intensional conciseness for PGxLOD took 0.23283743858337402s
Security | Sign check for PGxLOD took 0.16341686248779297s
Availability | Check URIs Dereferenciability for PGxLOD took 1541.6277720928192s
Completeness | Calculation of interlinking completeness for PGxLOD took 1.4333469867706299s
Reputation | Calculation of the PageRank for PGxLOD took 0.021408796310424805s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 9.5367431640625e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 56.12122559547424s
Believability | Calculation of trust value for PGxLOD took 8.106231689453125e-06s
INFO | --- Analysis for PGxLOD took 2862.1838269233704s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 2.102311134338379s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.24304676055908203s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020943880081176758s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 0.000110626220703125s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 7.62939453125e-06s
INFO | --- Analysis for phoible took 7.497100591659546s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.2438507080078125e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.23689746856689453s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.020451784133911133s
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.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.8371810913085938e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 7.62939453125e-06s
INFO | --- Analysis for PISM took 11.673598527908325s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.458427429199219e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2354896068572998s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020888805389404297s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 0.00010013580322265625s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.152557373046875e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.217783212661743s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.2009351253509521s
Availability | VoID file availability check for digitized plant specimen took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.22896647453308105s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.081031799316406e-05s
Believability | Calculation of trust value for digitized plant specimen took 8.58306884765625e-06s
INFO | --- Analysis for plant-specimen took 3.3325552940368652s
Availability | SPARQL endpoint availability check for Pleiades took 4.38690185546875e-05s
Availability | VoID file availability check for Pleiades took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Pleiades took 0.24069595336914062s
Reputation | Calculation of the PageRank for Pleiades took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.893013000488281e-05s
Believability | Calculation of trust value for Pleiades took 8.58306884765625e-06s
INFO | --- Analysis for pleiades took 14.258055448532104s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.267692565917969e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0007927417755126953s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.24634933471679688s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.314018249511719e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.62939453125e-06s
INFO | --- Analysis for podorozhnyk took 3.6453323364257812s
Availability | SPARQL endpoint availability check for Poképédia took 4.4345855712890625e-05s
Availability | VoID file availability check for Poképédia took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2467050552368164s
Reputation | Calculation of the PageRank for Poképédia took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0008428096771240234s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.963180541992188e-05s
Believability | Calculation of trust value for Poképédia took 7.62939453125e-06s
INFO | --- Analysis for pokepedia-fr took 2.344855785369873s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.4345855712890625e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.6746222972869873s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.987022399902344e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.775161743164062e-06s
INFO | --- Analysis for polymath-virtual-library took 5.712432146072388s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.8308498859405518s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.24237489700317383s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3113021850585938e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.62939453125e-06s
INFO | --- Analysis for portuguese_prisons_releases took 6.603846073150635s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.2438507080078125e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.24909210205078125s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.02108907699584961s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.147125244140625e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 8.106231689453125e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.641749382019043s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.3392181396484375e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2509133815765381s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.0994415283203125e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 8.106231689453125e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.636564016342163s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 5.984306335449219e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.24068856239318848s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 3.0279159545898438e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 7.867813110351562e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.624701738357544s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 3.981590270996094e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.24146747589111328s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.123283386230469e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.6272168159484863s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2424168586730957s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020718812942504883s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.6403186321258545s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 5.14984130859375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.24104762077331543s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.6379992961883545s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.100799560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.24398112297058105s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0008566379547119141s
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 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.6435461044311523s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.24186325073242188s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020977497100830078s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.361701965332031e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.651907444000244s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.23799490928649902s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.021161317825317383s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.218650817871094e-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 2.6416783332824707s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2448413372039795s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0008339881896972656s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.6450939178466797s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 5.602836608886719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2368028163909912s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.621809959411621s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.24143385887145996s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 1.1444091796875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.639798164367676s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2390434741973877s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.616274118423462s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.23852276802062988s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.147125244140625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.616861581802368s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.23967719078063965s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.02110457420349121s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0009164810180664062s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.790855407714844e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.635075330734253s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.23854589462280273s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.218650817871094e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.614492177963257s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.2401421070098877s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.0209043025970459s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.0279159545898438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.6425578594207764s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00039768218994140625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.23775696754455566s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 6.4373016357421875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.615539312362671s
Availability | SPARQL endpoint availability check for prefix.cc took 4.2438507080078125e-05s
Availability | VoID file availability check for prefix.cc took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.24434161186218262s
Reputation | Calculation of the PageRank for prefix.cc took 0.020923137664794922s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.100799560546875e-05s
Believability | Calculation of trust value for prefix.cc took 7.152557373046875e-06s
INFO | --- Analysis for prefix-cc took 3.0483434200286865s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 2.084709405899048s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2431783676147461s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020862579345703125s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 5.2928924560546875e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 6.9141387939453125e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 11.86335039138794s
Availability | SPARQL endpoint availability check for PreLex took 3.878787040710449s
Availability | VoID file availability check for PreLex took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for PreLex took 0.24559974670410156s
Reputation | Calculation of the PageRank for PreLex took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.128715515136719e-05s
Believability | Calculation of trust value for PreLex took 8.344650268554688e-06s
INFO | --- Analysis for prelex took 11.586688041687012s
Availability | SPARQL endpoint availability check for Prelinger Archives took 3.0997068881988525s
Availability | VoID file availability check for Prelinger Archives took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.23822855949401855s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 2.956390380859375e-05s
Believability | Calculation of trust value for Prelinger Archives took 7.152557373046875e-06s
INFO | --- Analysis for prelinger_archives took 10.922139644622803s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.8272786140441895s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.24179840087890625s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 4.839897155761719e-05s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 7.3909759521484375e-06s
INFO | --- Analysis for premon took 5.060988426208496s
Availability | SPARQL endpoint availability check for Previsible took 4.2438507080078125e-05s
Availability | VoID file availability check for Previsible took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Previsible took 0.24070978164672852s
Reputation | Calculation of the PageRank for Previsible took 0.02095651626586914s
Interlinking | Calculation of Degree of Connection for Previsible took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0008893013000488281s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.2159347534179688e-05s
Believability | Calculation of trust value for Previsible took 7.62939453125e-06s
INFO | --- Analysis for Previsible took 2.14609956741333s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.291534423828125e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.23523831367492676s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020355701446533203s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 6.651878356933594e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 8.344650268554688e-06s
INFO | --- Analysis for princeton-library-findingaids took 3.6136837005615234s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.4766225814819336s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.2419271469116211s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.000858306884765625s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 4.100799560546875e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for PrinParLat took 4.004271507263184s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.47113466262817383s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.23705577850341797s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.177757263183594e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.62939453125e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.168034315109253s
Availability | SPARQL endpoint availability check for Prior Panel took 4.267692565917969e-05s
Availability | VoID file availability check for Prior Panel took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.23940229415893555s
Reputation | Calculation of the PageRank for Prior Panel took 0.02113485336303711s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.504753112792969e-05s
Believability | Calculation of trust value for Prior Panel took 7.3909759521484375e-06s
INFO | --- Analysis for Prior_Panel took 2.174210786819458s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.553794860839844e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.2410876750946045s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.02103424072265625s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.218650817871094e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 7.152557373046875e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.627565383911133s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.315376281738281e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.23959708213806152s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.528594970703125e-05s
Believability | Calculation of trust value for Procomún SPARQL took 7.152557373046875e-06s
INFO | --- Analysis for procomun-sparql took 2.62896466255188s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.2393171787261963s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.021274089813232422s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.266334533691406e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 8.344650268554688e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.6141128540039062s
Availability | SPARQL endpoint availability check for ProductDB took 2.7970516681671143s
Availability | VoID file availability check for ProductDB took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for ProductDB took 0.24287676811218262s
Reputation | Calculation of the PageRank for ProductDB took 0.020861387252807617s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.700920104980469e-05s
Believability | Calculation of trust value for ProductDB took 9.059906005859375e-06s
INFO | --- Analysis for productdb took 6.378400564193726s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.24674677848815918s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.021230220794677734s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.0108642578125e-05s
Believability | Calculation of trust value for Product Types Ontology took 7.867813110351562e-06s
INFO | --- Analysis for productontology took 3.0376386642456055s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.23920154571533203s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.0274960994720459s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0011827945709228516s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.000118255615234375s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 3.966850996017456s
Availability | SPARQL endpoint availability check for provenanceweb took 0.04272818565368652s
Availability | VoID file availability check for provenanceweb took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.24121475219726562s
Reputation | Calculation of the PageRank for provenanceweb took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.462501525878906e-05s
Believability | Calculation of trust value for provenanceweb took 7.62939453125e-06s
INFO | --- Analysis for provenanceweb took 47.04928708076477s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.267692565917969e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.24138736724853516s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.0208282470703125s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010371208190917969s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 7.152557373046875e-06s
INFO | --- Analysis for proyectoapadrina took 3.726742744445801s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 24.98138689994812s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008456707000732422s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.31473755836486816s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.021434783935546875s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.910064697265625e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 5.4836273193359375e-06s
INFO | --- Analysis for pscs-catalogue took 123.91079807281494s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.3392181396484375e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.24270057678222656s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.414817810058594e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.1920928955078125e-05s
INFO | --- Analysis for psh-subject-headings took 2.4961392879486084s
Availability | SPARQL endpoint availability check for Depression took 0.34594082832336426s
Availability | VoID file availability check for Depression took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for Depression took 0.24098420143127441s
Reputation | Calculation of the PageRank for Depression took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Depression took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Depression took 3.147125244140625e-05s
Believability | Calculation of trust value for Depression took 7.62939453125e-06s
INFO | --- Analysis for Psychology took 2.5116145610809326s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.23829102516174316s
Reputation | Calculation of the PageRank for PubChem RDF took 0.02071237564086914s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.029273986816406e-05s
Believability | Calculation of trust value for PubChem RDF took 7.62939453125e-06s
INFO | --- Analysis for PubChem_RDF took 4.7619781494140625s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.124641418457031e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.23588204383850098s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.021002531051635742s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.9802322387695312e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 1.3828277587890625e-05s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.624375581741333s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.5065054893493652s
Availability | VoID file availability check for Public Spending in Greece took 0.0007915496826171875s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.24377822875976562s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.273124694824219e-05s
Believability | Calculation of trust value for Public Spending in Greece took 7.152557373046875e-06s
INFO | --- Analysis for public-spending-in-greece took 7.614190101623535s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.100799560546875e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.23516416549682617s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 3.1948089599609375e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 8.106231689453125e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.6351120471954346s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.22957849502563477s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006382465362548828s
Extra | Recovery of all triples for Publications Office Authority tables took 99.05798053741455s
Performance | Total latancy measurement for Publications Office Authority tables took 0.510901689529419s
Amount of data | Number of triples check for Publications Office Authority tables took 83.62566900253296s
Interoperability | New terms check for Publications Office Authority tables took 105.08521604537964s
Versatility | Languages check for Publications Office Authority tables took 300.1462228298187s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 1.0493130683898926s
Security | Check HTTPS for Publications Office Authority tables took 0.31568264961242676s
Interpretability | RDF structures check for Publications Office Authority tables took 0.3546154499053955s
Versatility | Serialization formats check for Publications Office Authority tables took 2.557203769683838s
Availability | RDF dump link check for Publications Office Authority tables took 0.25263404846191406s
License | MR license check for Publications Office Authority tables took 0.23994851112365723s
License | HR license check for Publications Office Authority tables took 300.08494424819946s
Amount of data | Number of property check for Publications Office Authority tables took 0.1671431064605713s
Understandability | Number of label check for Publications Office Authority tables took 5.721078634262085s
Understandability | URI regex check for Publications Office Authority tables took 0.4144856929779053s
Understandability | Vocabs check for Publications Office Authority tables took 0.0976104736328125s
Verifiability | Authors check for Publications Office Authority tables took 0.20118236541748047s
Verifiability | Publishers check for Publications Office Authority tables took 0.1730642318725586s
Performance | Throughput check for Publications Office Authority tables took 10.35170316696167s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.200241088867188e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.2277059555053711s
Interlinking | sameAs chians check for Publications Office Authority tables took 11.488362312316895s
Interlinking | skos check for Publications Office Authority tables took 0.5262284278869629s
Interlinking | skos check for Publications Office Authority tables took 0.44925928115844727s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.24648714065551758s
Currency | Creation date check for Publications Office Authority tables took 0.6563842296600342s
Currency | Modification date check for Publications Office Authority tables took 36.64194345474243s
Rep.Conc. | URIs length for Publications Office Authority tables took 492.41113805770874s
Interoperability | New vocabularies check for Publications Office Authority tables took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.15174293518066406s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.21652746200561523s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.2041187286376953s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 24.46706795692444s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.1296091079711914s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.5919573307037354s
Consistency | Disjoint class check for Publications Office Authority tables took 0.19694042205810547s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.36820912361145s
Consistency | Misplaced classes for Publications Office Authority tables took 8.374313831329346s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 35.18906092643738s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 11.529939889907837s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.3894991874695s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.088473081588745s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.5443630218505859s
Security | Sign check for Publications Office Authority tables took 0.14615654945373535s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 3.9302618503570557s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.0380744934082031s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.025927066802978516s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.220008850097656e-05s
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 5.245208740234375e-06s
INFO | --- Analysis for publications_office_authority_tables took 14682.6273355484s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.267692565917969e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.23828363418579102s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.6716461181640625e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 9.5367431640625e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 4.513742208480835s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.38690185546875e-05s
Availability | VoID file availability check for QBOAirbase took 0.0008852481842041016s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.6687071323394775s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020933151245117188s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.677078247070312e-05s
Believability | Calculation of trust value for QBOAirbase took 8.106231689453125e-06s
INFO | --- Analysis for qboairbase took 138.39606595039368s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.1961669921875e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.24296021461486816s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.9802322387695312e-05s
Believability | Calculation of trust value for qualitywebdata.org took 7.62939453125e-06s
INFO | --- Analysis for qualitywebdata-org took 4.033348560333252s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.363059997558594e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.23724699020385742s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.218650817871094e-05s
Believability | Calculation of trust value for Qualité de l'air took 6.9141387939453125e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.562448024749756s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.315376281738281e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0012652873992919922s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 1.3089509010314941s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.0248258113861084s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.1948089599609375e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 8.106231689453125e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 1316.9307885169983s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 180.52308535575867s
Availability | VoID file availability check for Querolus in LiLa took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.24054241180419922s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Querolus in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for Querolus took 315.5510256290436s
Availability | SPARQL endpoint availability check for Quotations Book took 5.1975250244140625e-05s
Availability | VoID file availability check for Quotations Book took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.7089591026306152s
Reputation | Calculation of the PageRank for Quotations Book took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.0040740966796875e-05s
Believability | Calculation of trust value for Quotations Book took 8.106231689453125e-06s
INFO | --- Analysis for quotations_book took 3.612961530685425s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.24245524406433105s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 8.58306884765625e-06s
INFO | --- Analysis for r4r took 3.1917474269866943s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.6500108242034912s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007340908050537109s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2442610263824463s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020814180374145508s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.744529724121094e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.2874603271484375e-05s
INFO | --- Analysis for racai-legalnero took 4.979395866394043s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.839897155761719e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.28362512588500977s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.457069396972656e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-corola-we took 21.343220710754395s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 85.3475432395935s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.6902928352355957s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020305871963500977s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 2.86102294921875e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 7.3909759521484375e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 97.80338978767395s
Availability | SPARQL endpoint availability check for RoLEX took 60.54951763153076s
Availability | VoID file availability check for RoLEX took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for RoLEX took 0.25265002250671387s
Reputation | Calculation of the PageRank for RoLEX took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.123283386230469e-05s
Believability | Calculation of trust value for RoLEX took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-rolex took 74.44637322425842s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0007791519165039062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2482738494873047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02094864845275879s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0010251998901367188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 20.36445665359497s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.2438507080078125e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.24169373512268066s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.123283386230469e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 12.44044542312622s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.3392181396484375e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.6955413818359375s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.123283386230469e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 15.826548337936401s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.267692565917969e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.263491153717041s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.0517578125e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 7.846370458602905s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.48256707191467285s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.24424982070922852s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.0279159545898438e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 8.344650268554688e-06s
INFO | --- Analysis for racai-llod-rtasc took 9.779128313064575s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.4443347454071045s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.24230146408081055s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 3.123283386230469e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-simonero took 3.1647934913635254s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.18762874603271484s
Availability | VoID file availability check for Rådata nå! took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2574806213378906s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 7.963180541992188e-05s
Believability | Calculation of trust value for Rådata nå! took 7.152557373046875e-06s
INFO | --- Analysis for radatana took 4.303156137466431s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 5.412101745605469e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.28098273277282715s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.021175622940063477s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.981590270996094e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 7.3909759521484375e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 16.08930015563965s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.172325134277344e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.24565410614013672s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 2.8848648071289062e-05s
Believability | Calculation of trust value for Raphael Research Resource took 8.106231689453125e-06s
INFO | --- Analysis for raphaelresearchresource took 3.1494650840759277s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.092633724212646s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.25043773651123047s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.0040740966796875e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.0013580322265625e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 26.27953600883484s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 391.96916103363037s
Availability | VoID file availability check for Polish LGU financial statements took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.24256086349487305s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.020949125289916992s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.337860107421875e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 7.3909759521484375e-06s
INFO | --- Analysis for Rb_PL_LGU took 666.905412197113s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.506111145019531e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.6824612617492676s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 2.765655517578125e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 4.4434592723846436s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.24265551567077637s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.03335285186767578s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0009477138519287109s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 6.580352783203125e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 4.013129472732544s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.23856449127197266s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 3.5336174964904785s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.24431133270263672s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 2.8133392333984375e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 3.094348192214966s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.172325134277344e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.23971128463745117s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 2.86102294921875e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 7.62939453125e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.66375994682312s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.2438507080078125e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.00048828125s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.24506354331970215s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.368492126464844e-05s
Believability | Calculation of trust value for RDF Book Mashup took 7.152557373046875e-06s
INFO | --- Analysis for rdf-book-mashup took 3.2070322036743164s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.3392181396484375e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.24070334434509277s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010061264038085938s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 7.3909759521484375e-06s
INFO | --- Analysis for rdfize-lastfm took 2.216916561126709s
Availability | SPARQL endpoint availability check for RDFLicense took 262.0222444534302s
Availability | VoID file availability check for RDFLicense took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.24665021896362305s
Reputation | Calculation of the PageRank for RDFLicense took 0.02090764045715332s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.695487976074219e-05s
Believability | Calculation of trust value for RDFLicense took 7.867813110351562e-06s
INFO | --- Analysis for rdflicense took 536.9278118610382s
Availability | SPARQL endpoint availability check for RDFohloh took 4.8160552978515625e-05s
Availability | VoID file availability check for RDFohloh took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2617776393890381s
Reputation | Calculation of the PageRank for RDFohloh took 0.021044254302978516s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.965896606445312e-05s
Believability | Calculation of trust value for RDFohloh took 7.867813110351562e-06s
INFO | --- Analysis for rdfohloh took 7.427866458892822s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.5292179584503174s
Availability | VoID file availability check for Reactome RDF took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.24504303932189941s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 4.4345855712890625e-05s
Believability | Calculation of trust value for Reactome RDF took 7.867813110351562e-06s
INFO | --- Analysis for reactome-rdf took 3.8384017944335938s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 300.2169408798218s
Availability | VoID file availability check for Rechtspraak.nl took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.24284720420837402s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.022023916244506836s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00010228157043457031s
Believability | Calculation of trust value for Rechtspraak.nl took 5.0067901611328125e-06s
INFO | --- Analysis for rechtspraak took 304.60462856292725s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.267692565917969e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2442305088043213s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.821487426757812e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 7.62939453125e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 8.879410743713379s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.06798648834228516s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.25408482551574707s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001533031463623047s
Believability | Calculation of trust value for reference.data.gov.uk took 5.9604644775390625e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.80802059173584s
Availability | SPARQL endpoint availability check for Regiony took 4.00543212890625e-05s
Availability | VoID file availability check for Regiony took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Regiony took 0.23238587379455566s
Reputation | Calculation of the PageRank for Regiony took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for Regiony took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Regiony took 2.8848648071289062e-05s
Believability | Calculation of trust value for Regiony took 7.152557373046875e-06s
INFO | --- Analysis for regiony took 3.08491587638855s
Availability | SPARQL endpoint availability check for RELD took 262.12632417678833s
Availability | VoID file availability check for RELD took 0.0003101825714111328s
Completeness | Calculation of interlinking completeness for RELD took 0.24287986755371094s
Reputation | Calculation of the PageRank for RELD took 0.02130126953125s
Interlinking | Calculation of Degree of Connection for RELD took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RELD took 0.0009186267852783203s
Interlinking | Calculation of Clustering coefficient for RELD took 3.4332275390625e-05s
Believability | Calculation of trust value for RELD took 7.62939453125e-06s
INFO | --- Analysis for RELD took 536.7975497245789s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.35808873176574707s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005202293395996094s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.485464096069336s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.5998682975769043s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.3841748237609863s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.5379908084869385s
Versatility | Languages check for Repository for Linked Open Archival Data took 5.423991680145264s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.3859269618988037s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.22120046615600586s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.3050377368927002s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.27268004417419434s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.20516705513000488s
License | MR license check for Repository for Linked Open Archival Data took 0.33426356315612793s
License | HR license check for Repository for Linked Open Archival Data took 7.476951599121094s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.2905271053314209s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.8482918739318848s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.48674535751342773s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.13834857940673828s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.1804358959197998s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.1870260238647461s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.629671096801758s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 7.843971252441406e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.06913089752197266s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.14617705345153809s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.3989098072052002s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.13912487030029297s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.27593517303466797s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.24286699295043945s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.36721301078796387s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.8477962017059326s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.09833931922912598s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.10409975051879883s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.07989692687988281s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.33054208755493164s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.029074907302856445s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028299808502197266s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.16506624221801758s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.8104097843170166s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.24429035186767578s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.6782145500183105s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.1374919414520264s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 2.9539012908935547s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.030444860458374023s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.11137223243713379s
Security | Sign check for Repository for Linked Open Archival Data took 0.4100463390350342s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 2446.535307407379s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.9369816780090332s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.022786617279052734s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 9.846687316894531e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 8.344650268554688e-06s
INFO | --- Analysis for reload took 2564.4470961093903s
Availability | SPARQL endpoint availability check for Land use merced dataset took 5.0067901611328125e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.6706724166870117s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for Land use merced dataset took 7.62939453125e-06s
INFO | --- Analysis for remote_Sensing took 13.406857252120972s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.6762185096740723s
Availability | VoID file availability check for Renewable Energy Generators took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.24761962890625s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.02082085609436035s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 5.626678466796875e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 6.198883056640625e-06s
INFO | --- Analysis for renewable_energy_generators took 8.717703580856323s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.05056571960449219s
Availability | VoID file availability check for research.data.gov.uk took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.24666571617126465s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.226799011230469e-05s
Believability | Calculation of trust value for research.data.gov.uk took 1.0251998901367188e-05s
INFO | --- Analysis for research-data-gov-uk took 2.7456588745117188s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 9.512901306152344e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2421705722808838s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.021338701248168945s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.0279159545898438e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 7.867813110351562e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 2.757660388946533s
Availability | SPARQL endpoint availability check for Restaurantes took 4.076957702636719e-05s
Availability | VoID file availability check for Restaurantes took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.2427830696105957s
Reputation | Calculation of the PageRank for Restaurantes took 0.020847320556640625s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.981590270996094e-05s
Believability | Calculation of trust value for Restaurantes took 7.152557373046875e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.650487184524536s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.38690185546875e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.24740958213806152s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.021355390548706055s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 7.319450378417969e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 3.867619752883911s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.051018714904785156s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.23920702934265137s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.0994415283203125e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 7.3909759521484375e-06s
INFO | --- Analysis for revistas_turismo took 2.2665069103240967s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.24263930320739746s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0008370876312255859s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.24102187156677246s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.02095770835876465s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0008475780487060547s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00012969970703125s
Believability | Calculation of trust value for Revyu.com - Review Anything took 8.106231689453125e-06s
INFO | --- Analysis for revyu took 2.423595905303955s
Availability | SPARQL endpoint availability check for sdafsadf took 0.3046073913574219s
Availability | VoID file availability check for sdafsadf took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.2389998435974121s
Reputation | Calculation of the PageRank for sdafsadf took 0.021054506301879883s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.170967102050781e-05s
Believability | Calculation of trust value for sdafsadf took 8.106231689453125e-06s
INFO | --- Analysis for rgsdfg took 2.8889310359954834s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.00010228157043457031s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2614734172821045s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.6253204345703125e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 8.344650268554688e-06s
INFO | --- Analysis for riese took 2.290281057357788s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.291534423828125e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.24887490272521973s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 9.059906005859375e-06s
INFO | --- Analysis for rijksmuseum took 2.7099862098693848s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.5367751121520996s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.23521018028259277s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.02068185806274414s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.482269287109375e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 8.344650268554688e-06s
INFO | --- Analysis for rism took 3.2298483848571777s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.1729898452758789s
Availability | VoID file availability check for RISM Authority data took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.23938488960266113s
Reputation | Calculation of the PageRank for RISM Authority data took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.601478576660156e-05s
Believability | Calculation of trust value for RISM Authority data took 7.3909759521484375e-06s
INFO | --- Analysis for rism-authorities took 3.9084017276763916s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.487701416015625e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.24265360832214355s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.62939453125e-06s
INFO | --- Analysis for rk took 2.162815809249878s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.03704380989074707s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.24315690994262695s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.000232696533203125s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.2672693729400635s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.03487563133239746s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2487044334411621s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.021158933639526367s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00014543533325195312s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.258955717086792s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.04187893867492676s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2374258041381836s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.02100539207458496s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0002014636993408203s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.242710590362549s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0414888858795166s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2404310703277588s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00015854835510253906s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.255237102508545s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.04617881774902344s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.24122834205627441s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00017189979553222656s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.2625176906585693s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.04239082336425781s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.24317526817321777s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.02102375030517578s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.790855407714844e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.2303874492645264s
Availability | SPARQL endpoint availability check for crm took 7.43865966796875e-05s
Availability | VoID file availability check for crm took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for crm took 0.24459552764892578s
Reputation | Calculation of the PageRank for crm took 0.020949125289916992s
Interlinking | Calculation of Degree of Connection for crm took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for crm took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for crm took 3.147125244140625e-05s
Believability | Calculation of trust value for crm took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.7296407222747803s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.034063100814819336s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2347733974456787s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0001270771026611328s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.286226511001587s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.043859004974365234s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.24417757987976074s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.021005630493164062s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.602836608886719e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.278118133544922s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0431666374206543s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.25491929054260254s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002484321594238281s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.282754898071289s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04468560218811035s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.24143528938293457s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 0.0001068115234375s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.232424736022949s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.03496742248535156s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2379300594329834s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.021171092987060547s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.679794311523438e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.257368803024292s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.03599381446838379s
Availability | VoID file availability check for digitaleconomy took 0.00041961669921875s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.23659253120422363s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.123283386230469e-05s
Believability | Calculation of trust value for digitaleconomy took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.2139079570770264s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.08543753623962402s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.24214601516723633s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.0001475811004638672s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.2827820777893066s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.04442167282104492s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2641410827636719s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.022690773010253906s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0008687973022460938s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 7.534027099609375e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.6031105518341064s
Availability | SPARQL endpoint availability check for enaktingpsi took 5.221366882324219e-05s
Availability | VoID file availability check for enaktingpsi took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.24132323265075684s
Reputation | Calculation of the PageRank for enaktingpsi took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.0040740966796875e-05s
Believability | Calculation of trust value for enaktingpsi took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.6615419387817383s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.04488420486450195s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.24216270446777344s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00017881393432617188s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.3060359954833984s
Availability | SPARQL endpoint availability check for epsrc took 0.05058479309082031s
Availability | VoID file availability check for epsrc took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for epsrc took 0.24338269233703613s
Reputation | Calculation of the PageRank for epsrc took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for epsrc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for epsrc took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.698204040527344e-05s
Believability | Calculation of trust value for epsrc took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.277904748916626s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.04840874671936035s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0012781620025634766s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.27179861068725586s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.296966552734375e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-era took 2.341177225112915s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.058274269104003906s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.2440183162689209s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010228157043457031s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.2878003120422363s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 3.981590270996094e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.24564838409423828s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.0994415283203125e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-foreign took 2.63698410987854s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.07301545143127441s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2402479648590088s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.916854858398438e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.3038437366485596s
Availability | SPARQL endpoint availability check for fun took 0.045659542083740234s
Availability | VoID file availability check for fun took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for fun took 0.24387693405151367s
Reputation | Calculation of the PageRank for fun took 0.020760059356689453s
Interlinking | Calculation of Degree of Connection for fun took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for fun took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for fun took 7.915496826171875e-05s
Believability | Calculation of trust value for fun took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.3101437091827393s
Availability | SPARQL endpoint availability check for gdlc took 0.05839228630065918s
Availability | VoID file availability check for gdlc took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for gdlc took 0.2376413345336914s
Reputation | Calculation of the PageRank for gdlc took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for gdlc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for gdlc took 8.106231689453125e-05s
Believability | Calculation of trust value for gdlc took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.318794012069702s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.043524742126464844s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.24005937576293945s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020783185958862305s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.0001163482666015625s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.3298494815826416s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.041489362716674805s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00042724609375s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.24814343452453613s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.02070307731628418s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001373291015625s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.277853012084961s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.04348492622375488s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.24394559860229492s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00014495849609375s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.354769706726074s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.03958010673522949s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2438340187072754s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.222724914550781e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.267568826675415s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.0362851619720459s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2459414005279541s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0008249282836914062s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.462501525878906e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.268655776977539s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.051229000091552734s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2438678741455078s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.315376281738281e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.2770183086395264s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0338435173034668s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.25213098526000977s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016260147094726562s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.294306993484497s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.044754981994628906s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.249220609664917s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00015282630920410156s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.32808256149292s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.043416500091552734s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.23803162574768066s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.021107912063598633s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.723403930664062e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.2622122764587402s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.04307866096496582s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.25119805335998535s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.021267414093017578s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001652240753173828s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.2614405155181885s
Availability | SPARQL endpoint availability check for notube took 0.0380558967590332s
Availability | VoID file availability check for notube took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for notube took 0.2595036029815674s
Reputation | Calculation of the PageRank for notube took 0.02100658416748047s
Interlinking | Calculation of Degree of Connection for notube took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for notube took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for notube took 4.4345855712890625e-05s
Believability | Calculation of trust value for notube took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.2613861560821533s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.06606245040893555s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.24434685707092285s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00013446807861328125s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.280641555786133s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.03256392478942871s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2590606212615967s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015592575073242188s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.298840284347534s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.23833370208740234s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.684706449508667s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.03513598442077637s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.23029375076293945s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.605552673339844e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-os took 2.231213092803955s
Availability | SPARQL endpoint availability check for photos took 0.04228925704956055s
Availability | VoID file availability check for photos took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for photos took 0.23999929428100586s
Reputation | Calculation of the PageRank for photos took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for photos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for photos took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for photos took 7.319450378417969e-05s
Believability | Calculation of trust value for photos took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.2200872898101807s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04188060760498047s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0009596347808837891s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.23945116996765137s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02085137367248535s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.0001163482666015625s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.280863046646118s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.033774614334106445s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2395002841949463s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020975589752197266s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019502639770507812s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.259744167327881s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.03523826599121094s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.24124431610107422s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00013709068298339844s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.2437310218811035s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.0407862663269043s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.2501966953277588s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.083747863769531e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.303820848464966s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.037355661392211914s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2415933609008789s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012946128845214844s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.3600375652313232s
Availability | SPARQL endpoint availability check for roni took 0.0425114631652832s
Availability | VoID file availability check for roni took 0.0003554821014404297s
Completeness | Calculation of interlinking completeness for roni took 0.23990273475646973s
Reputation | Calculation of the PageRank for roni took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for roni took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for roni took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for roni took 3.1948089599609375e-05s
Believability | Calculation of trust value for roni took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.264224052429199s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.037160396575927734s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.23420238494873047s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00022411346435546875s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.2112064361572266s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04114866256713867s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.22812700271606445s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00011014938354492188s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.2790699005126953s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.10607028007507324s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.4895355701446533s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.021456003189086914s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0008943080902099609s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00012612342834472656s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 4.475481033325195s
Availability | SPARQL endpoint availability check for webconf took 0.09387755393981934s
Availability | VoID file availability check for webconf took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for webconf took 0.2669026851654053s
Reputation | Calculation of the PageRank for webconf took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for webconf took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for webconf took 0.0001354217529296875s
Believability | Calculation of trust value for webconf took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-webconf took 13.914264678955078s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.03424382209777832s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.22831511497497559s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02100062370300293s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.295608520507812e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.2164254188537598s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04549837112426758s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.23374342918395996s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00020933151245117188s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.2012875080108643s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.0456392765045166s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.000244140625s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.2298107147216797s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.021145105361938477s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0008072853088378906s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 0.00010538101196289062s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.2073373794555664s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.267692565917969e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.23719382286071777s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020925045013427734s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for RKB Explorer Data took 8.58306884765625e-06s
INFO | --- Analysis for rkb_explorer_data took 2.597688913345337s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.4203145503997803s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.23377513885498047s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.020825624465942383s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.0108642578125e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 8.106231689453125e-06s
INFO | --- Analysis for roceeh-road took 3.365464925765991s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.267692565917969e-05s
Availability | VoID file availability check for The Rosetta Project took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.23208308219909668s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.1948089599609375e-05s
Believability | Calculation of trust value for The Rosetta Project took 7.867813110351562e-06s
INFO | --- Analysis for rosetta-project took 2.5787739753723145s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 7.2479248046875e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0004057884216308594s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.2338428497314453s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.147125244140625e-05s
Believability | Calculation of trust value for ontology terrorist attack took 6.67572021484375e-06s
INFO | --- Analysis for ROSHANI took 3.346712589263916s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.458427429199219e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.23216938972473145s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.457069396972656e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 8.106231689453125e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.1366219520568848s
Availability | SPARQL endpoint availability check for x took 4.482269287109375e-05s
Availability | VoID file availability check for x took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for x took 0.22944855690002441s
Reputation | Calculation of the PageRank for x took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for x took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for x took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for x took 3.075599670410156e-05s
Believability | Calculation of trust value for x took 7.62939453125e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.085987091064453s
Availability | SPARQL endpoint availability check for Rpm Find took 4.0531158447265625e-05s
Availability | VoID file availability check for Rpm Find took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.23432326316833496s
Reputation | Calculation of the PageRank for Rpm Find took 0.022565841674804688s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0010328292846679688s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.814697265625e-05s
Believability | Calculation of trust value for Rpm Find took 8.821487426757812e-06s
INFO | --- Analysis for rpm_find took 2.610382318496704s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 0.00011157989501953125s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0004143714904785156s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.24203777313232422s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02083301544189453s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 7.224082946777344e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.867813110351562e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.714569091796875s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.267692565917969e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.251849889755249s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.02077198028564453s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.748603820800781e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 7.867813110351562e-06s
INFO | --- Analysis for rubentaelman took 2.5804452896118164s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.363059997558594e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0003490447998046875s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.23496723175048828s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.440017700195312e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 8.344650268554688e-06s
INFO | --- Analysis for rubenverborgh took 2.8720335960388184s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 393.02076387405396s
Availability | VoID file availability check for Russian Universities Specialities took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.2757112979888916s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.0209805965423584s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.172325134277344e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 7.3909759521484375e-06s
INFO | --- Analysis for russian-universities-specialities took 678.1618919372559s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.410743713378906e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.2586946487426758s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.020859479904174805s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.3855438232421875e-05s
Believability | Calculation of trust value for RuThes Cloud took 6.9141387939453125e-06s
INFO | --- Analysis for ruthes took 4.932657480239868s
Availability | SPARQL endpoint availability check for RxNorm took 4.100799560546875e-05s
Availability | VoID file availability check for RxNorm took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for RxNorm took 0.23745322227478027s
Reputation | Calculation of the PageRank for RxNorm took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.504753112792969e-05s
Believability | Calculation of trust value for RxNorm took 7.3909759521484375e-06s
INFO | --- Analysis for rxnorm took 3.548016309738159s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.513918876647949s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.23233914375305176s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 2.956390380859375e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 7.62939453125e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 9.77791976928711s
Availability | SPARQL endpoint availability check for SALDO took 4.124641418457031e-05s
Availability | VoID file availability check for SALDO took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for SALDO took 0.23965048789978027s
Reputation | Calculation of the PageRank for SALDO took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for SALDO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.075599670410156e-05s
Believability | Calculation of trust value for SALDO took 7.3909759521484375e-06s
INFO | --- Analysis for saldo took 3.1486730575561523s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.065725326538086s
Availability | VoID file availability check for SALDO-RDF took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2401890754699707s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for SALDO-RDF took 7.3909759521484375e-06s
INFO | --- Analysis for saldo-rdf took 5.353498458862305s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.7068238258361816s
Availability | VoID file availability check for SALDOM-RDF took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.23867464065551758s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020832300186157227s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.4332275390625e-05s
Believability | Calculation of trust value for SALDOM-RDF took 7.867813110351562e-06s
INFO | --- Analysis for saldom-rdf took 4.723659992218018s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 8.821487426757812e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.6856942176818848s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.020794153213500977s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010895729064941406s
Believability | Calculation of trust value for Salzburgerland DE took 7.152557373046875e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.2221477031707764s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.220008850097656e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.2411024570465088s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00011157989501953125s
Believability | Calculation of trust value for Salzburgerland EN took 7.3909759521484375e-06s
INFO | --- Analysis for salzburgerland-com-en took 2.64164662361145s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.4345855712890625e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.24729084968566895s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.03272271156311035s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0011696815490722656s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00015020370483398438s
Believability | Calculation of trust value for Salzburgerland IT took 7.3909759521484375e-06s
INFO | --- Analysis for salzburgerland-com-it took 2.6541025638580322s
Availability | SPARQL endpoint availability check for sameAs.org took 4.267692565917969e-05s
Availability | VoID file availability check for sameAs.org took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.2425706386566162s
Reputation | Calculation of the PageRank for sameAs.org took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 2.9802322387695312e-05s
Believability | Calculation of trust value for sameAs.org took 7.867813110351562e-06s
INFO | --- Analysis for sameas-org took 2.6903295516967773s
Availability | SPARQL endpoint availability check for sandrart.net took 4.4345855712890625e-05s
Availability | VoID file availability check for sandrart.net took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.24004125595092773s
Reputation | Calculation of the PageRank for sandrart.net took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 7.128715515136719e-05s
Believability | Calculation of trust value for sandrart.net took 6.9141387939453125e-06s
INFO | --- Analysis for sandrart-net took 3.424818515777588s
Availability | SPARQL endpoint availability check for Taxons  took 0.22014474868774414s
Availability | VoID file availability check for Taxons  took 0.000682830810546875s
Extra | Recovery of all triples for Taxons  took 25.789419889450073s
Performance | Total latancy measurement for Taxons  took 0.3909482955932617s
Amount of data | Number of triples check for Taxons  took 2.874708890914917s
Interoperability | New terms check for Taxons  took 2.0723936557769775s
Versatility | Languages check for Taxons  took 44.831687450408936s
Interpretability | Number of blank nodes check for Taxons  took 1.001101016998291s
Security | Check HTTPS for Taxons  took 0.17905449867248535s
Interpretability | RDF structures check for Taxons  took 1.60392165184021s
Versatility | Serialization formats check for Taxons  took 1.1930510997772217s
Availability | RDF dump link check for Taxons  took 0.3694291114807129s
License | MR license check for Taxons  took 3.1279287338256836s
License | HR license check for Taxons  took 3.452265739440918s
Amount of data | Number of property check for Taxons  took 0.10718178749084473s
Understandability | Number of label check for Taxons  took 4.544435739517212s
Understandability | URI regex check for Taxons  took 1.1993064880371094s
Understandability | Vocabs check for Taxons  took 0.33256101608276367s
Verifiability | Authors check for Taxons  took 0.08210992813110352s
Verifiability | Publishers check for Taxons  took 0.07509160041809082s
Performance | Throughput check for Taxons  took 10.472594022750854s
Amount of data | Check the number of entities for Taxons  took 5.936622619628906e-05s
Verifiability | Contribs. check for Taxons  took 0.0759272575378418s
Interlinking | sameAs chians check for Taxons  took 0.1583254337310791s
Interlinking | skos check for Taxons  took 0.16663479804992676s
Interlinking | skos check for Taxons  took 0.08286857604980469s
Timeliness | dataset update frequency check for Taxons  took 0.5747489929199219s
Currency | Creation date check for Taxons  took 0.23441767692565918s
Currency | Modification date check for Taxons  took 0.23627400398254395s
Rep.Conc. | URIs length for Taxons  took 15.670107126235962s
Interoperability | New vocabularies check for Taxons  took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.10111474990844727s
Accuracy | Check Functional Property for Taxons  took 0.7581145763397217s
Accuracy | Check Inverse Functional Property for Taxons  took 0.4858837127685547s
Accuracy | Check Empty annotation labels for Taxons  took 5.1613829135894775s
Accuracy | Check White space in annotation for Taxons  took 0.30749940872192383s
Accuracy | Check Datatype consistency for Taxons  took 0.2684471607208252s
Consistency | Disjoint class check for Taxons  took 0.1420900821685791s
Consistency | Check Misplaced properties for Taxons  took 4.589571475982666s
Consistency | Misplaced classes for Taxons  took 0.9679281711578369s
Consistency | Check Ontology hijacking for Taxons  took 5.335506200790405s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.1932270526885986s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.928610801696777s
Conciseness | Check Extensional conciseness for Taxons  took 0.284440279006958s
Conciseness | Check Intensional conciseness for Taxons  took 0.17883586883544922s
Security | Sign check for Taxons  took 1.591080665588379s
Availability | Check URIs Dereferenciability for Taxons  took 1695.4672298431396s
Completeness | Calculation of interlinking completeness for Taxons  took 1.3125953674316406s
Reputation | Calculation of the PageRank for Taxons  took 0.021418333053588867s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.058547973632812e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 1.9073486328125e-06s
Believability | Calculation of trust value for Taxons  took 7.62939453125e-06s
INFO | --- Analysis for sandre took 1910.9044613838196s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.690932273864746s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.6766350269317627s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.075599670410156e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 8.40045428276062s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 262.14498567581177s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.6734633445739746s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.021221399307250977s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 8.344650268554688e-06s
INFO | --- Analysis for santillana_guide_dataset took 670.4777679443359s
Availability | SPARQL endpoint availability check for SATAR test  took 4.7206878662109375e-05s
Availability | VoID file availability check for SATAR test  took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.26369428634643555s
Reputation | Calculation of the PageRank for SATAR test  took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.0517578125e-05s
Believability | Calculation of trust value for SATAR test  took 7.867813110351562e-06s
INFO | --- Analysis for SATAR_test took 6.725265026092529s
Availability | SPARQL endpoint availability check for SCBG Data took 21.48659372329712s
Availability | VoID file availability check for SCBG Data took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.6965930461883545s
Reputation | Calculation of the PageRank for SCBG Data took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 9.870529174804688e-05s
Believability | Calculation of trust value for SCBG Data took 6.198883056640625e-06s
INFO | --- Analysis for SCBG-Data took 54.19944167137146s
Availability | SPARQL endpoint availability check for schema.org took 5.53131103515625e-05s
Availability | VoID file availability check for schema.org took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for schema.org took 0.23907470703125s
Reputation | Calculation of the PageRank for schema.org took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for schema.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for schema.org took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.6716461181640625e-05s
Believability | Calculation of trust value for schema.org took 7.867813110351562e-06s
INFO | --- Analysis for schema-org took 3.981506824493408s
Availability | SPARQL endpoint availability check for Schemantra took 4.315376281738281e-05s
Availability | VoID file availability check for Schemantra took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Schemantra took 0.24320054054260254s
Reputation | Calculation of the PageRank for Schemantra took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.8848648071289062e-05s
Believability | Calculation of trust value for Schemantra took 7.152557373046875e-06s
INFO | --- Analysis for Schemantra took 2.6181886196136475s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.5116767883300781s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.679485559463501s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.314018249511719e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 7.152557373046875e-06s
INFO | --- Analysis for schemapedia took 5.045273542404175s
Availability | SPARQL endpoint availability check for scholarlydata took 4.2438507080078125e-05s
Availability | VoID file availability check for scholarlydata took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.24175477027893066s
Reputation | Calculation of the PageRank for scholarlydata took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.9087066650390625e-05s
Believability | Calculation of trust value for scholarlydata took 1.2874603271484375e-05s
INFO | --- Analysis for scholarlydata took 2.672593832015991s
Availability | SPARQL endpoint availability check for Scholarometer took 4.410743713378906e-05s
Availability | VoID file availability check for Scholarometer took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2424921989440918s
Reputation | Calculation of the PageRank for Scholarometer took 0.02095341682434082s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 9.036064147949219e-05s
Believability | Calculation of trust value for Scholarometer took 7.3909759521484375e-06s
INFO | --- Analysis for scholarometer took 7.1943888664245605s
Availability | SPARQL endpoint availability check for Science Commons took 4.1961669921875e-05s
Availability | VoID file availability check for Science Commons took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Science Commons took 0.24007415771484375s
Reputation | Calculation of the PageRank for Science Commons took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Science Commons took 3.147125244140625e-05s
Believability | Calculation of trust value for Science Commons took 7.867813110351562e-06s
INFO | --- Analysis for science_commons took 2.6828930377960205s
Availability | SPARQL endpoint availability check for ScienceWise took 4.0531158447265625e-05s
Availability | VoID file availability check for ScienceWise took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.24151992797851562s
Reputation | Calculation of the PageRank for ScienceWise took 0.020843505859375s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0009169578552246094s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.528594970703125e-05s
Believability | Calculation of trust value for ScienceWise took 1.3113021850585938e-05s
INFO | --- Analysis for sciencewise took 2.6445565223693848s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.291534423828125e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.24259424209594727s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.956390380859375e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 5.0067901611328125e-06s
INFO | --- Analysis for scoreboard took 4.395578622817993s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.5299530029296875e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.24248909950256348s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.021042346954345703s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.170967102050781e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.106231689453125e-06s
INFO | --- Analysis for SDDEC took 15.164038181304932s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.291534423828125e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.24240422248840332s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.0279159545898438e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.821487426757812e-06s
INFO | --- Analysis for SDG took 3.496515989303589s
Availability | SPARQL endpoint availability check for sears.com took 4.2438507080078125e-05s
Availability | VoID file availability check for sears.com took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for sears.com took 0.25919413566589355s
Reputation | Calculation of the PageRank for sears.com took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for sears.com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for sears.com took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.818771362304688e-05s
Believability | Calculation of trust value for sears.com took 7.867813110351562e-06s
INFO | --- Analysis for sears took 3.8423807621002197s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.07938575744628906s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.24379920959472656s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.440017700195312e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.4836273193359375e-06s
INFO | --- Analysis for sec-rdfabout took 5.780739068984985s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.69058632850647s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0010449886322021484s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.3592662811279297s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.559226989746094e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for secold took 167.96051955223083s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.124641418457031e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.000244140625s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.24248981475830078s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 3.0994415283203125e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 7.3909759521484375e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.1119441986083984s
Availability | SPARQL endpoint availability check for semanlink took 4.2438507080078125e-05s
Availability | VoID file availability check for semanlink took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for semanlink took 0.24329471588134766s
Reputation | Calculation of the PageRank for semanlink took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for semanlink took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001480579376220703s
Believability | Calculation of trust value for semanlink took 7.152557373046875e-06s
INFO | --- Analysis for semanlink took 3.316498279571533s
Availability | SPARQL endpoint availability check for Semantic Library took 5.0067901611328125e-05s
Availability | VoID file availability check for Semantic Library took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.24759364128112793s
Reputation | Calculation of the PageRank for Semantic Library took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.9802322387695312e-05s
Believability | Calculation of trust value for Semantic Library took 6.67572021484375e-06s
INFO | --- Analysis for semantic-library took 3.1541554927825928s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.220008850097656e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.00034999847412109375s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.24487733840942383s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020835161209106445s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.0040740966796875e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 7.62939453125e-06s
INFO | --- Analysis for semantic-profiling-network took 2.6919565200805664s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.051535844802856445s
Availability | VoID file availability check for Semantic Universe Data took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.24050045013427734s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for Semantic Universe Data took 8.106231689453125e-06s
INFO | --- Analysis for semantic-universe took 2.329232692718506s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.45483946800232s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.24847888946533203s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00012063980102539062s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.1920928955078125e-05s
INFO | --- Analysis for semantic-web-dog-food took 82.83633589744568s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 5.507469177246094e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.26046204566955566s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.021030426025390625s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.553794860839844e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 7.152557373046875e-06s
INFO | --- Analysis for semantic-web-grundlagen took 2.760589361190796s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.482269287109375e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.24003291130065918s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.075599670410156e-05s
Believability | Calculation of trust value for semantic-web-journal took 8.58306884765625e-06s
INFO | --- Analysis for semantic-web-journal took 2.688948392868042s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.291534423828125e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.24153518676757812s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.988380432128906e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 5.0067901611328125e-06s
INFO | --- Analysis for semantic-xbrl took 3.1688997745513916s
Availability | SPARQL endpoint availability check for Semantic Bible took 5.435943603515625e-05s
Availability | VoID file availability check for Semantic Bible took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2508084774017334s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.147125244140625e-05s
Believability | Calculation of trust value for Semantic Bible took 7.152557373046875e-06s
INFO | --- Analysis for semantic_bible took 2.695599317550659s
Availability | SPARQL endpoint availability check for SemanticQuran took 7.01532244682312s
Availability | VoID file availability check for SemanticQuran took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.27559375762939453s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020869731903076172s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.224082946777344e-05s
Believability | Calculation of trust value for SemanticQuran took 7.867813110351562e-06s
INFO | --- Analysis for semanticquran took 16.675562381744385s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.482269287109375e-05s
Availability | VoID file availability check for SemanticTweet took 0.0007908344268798828s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.24342823028564453s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 6.580352783203125e-05s
Believability | Calculation of trust value for SemanticTweet took 7.867813110351562e-06s
INFO | --- Analysis for semantictweet took 3.793283700942993s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.3392181396484375e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.24843072891235352s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.843971252441406e-05s
Believability | Calculation of trust value for semanticweb.org took 7.3909759521484375e-06s
INFO | --- Analysis for semanticweb-org took 22.336859464645386s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.08169436454772949s
Availability | VoID file availability check for Semantic CrunchBase took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.24155759811401367s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 7.05718994140625e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 7.3909759521484375e-06s
INFO | --- Analysis for semsol-crunchbase took 2.3016128540039062s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.1484832763671875e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.23976564407348633s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0008695125579833984s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.504753112792969e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 7.867813110351562e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.6504712104797363s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2569386959075928s
Availability | VoID file availability check for SentimentWortschatz took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2381443977355957s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.267692565917969e-05s
Believability | Calculation of trust value for SentimentWortschatz took 7.867813110351562e-06s
INFO | --- Analysis for sentiws took 3.985651969909668s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.00693917274475s
Availability | VoID file availability check for seoul-bike-data took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.23654913902282715s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.0040740966796875e-05s
Believability | Calculation of trust value for seoul-bike-data took 6.9141387939453125e-06s
INFO | --- Analysis for seoul-bike-data took 72.27763986587524s
Availability | SPARQL endpoint availability check for Serendipity took 8.133907318115234s
Availability | VoID file availability check for Serendipity took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Serendipity took 0.24073529243469238s
Reputation | Calculation of the PageRank for Serendipity took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for Serendipity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Serendipity took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.081031799316406e-05s
Believability | Calculation of trust value for Serendipity took 7.867813110351562e-06s
INFO | --- Analysis for serendipity took 15.562042474746704s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.363059997558594e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.23948001861572266s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.021532535552978516s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0011067390441894531s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.719329833984375e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.2874603271484375e-05s
INFO | --- Analysis for Sherry_Wine took 2.367722749710083s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.267692565917969e-05s
Availability | VoID file availability check for Sherry Wine took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.23953533172607422s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020669937133789062s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.0040740966796875e-05s
Believability | Calculation of trust value for Sherry Wine took 7.867813110351562e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.1555817127227783s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.8551120758056641s
Availability | VoID file availability check for Shoah victims? names took 0.0005033016204833984s
Extra | Recovery of all triples for Shoah victims? names took 1.3954339027404785s
Performance | Total latancy measurement for Shoah victims? names took 0.5962803363800049s
Amount of data | Number of triples check for Shoah victims? names took 1.3602690696716309s
Interoperability | New terms check for Shoah victims? names took 1.509979248046875s
Versatility | Languages check for Shoah victims? names took 6.199088096618652s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.118746280670166s
Security | Check HTTPS for Shoah victims? names took 0.5901508331298828s
Interpretability | RDF structures check for Shoah victims? names took 0.27797436714172363s
Versatility | Serialization formats check for Shoah victims? names took 0.3010690212249756s
Availability | RDF dump link check for Shoah victims? names took 0.17496538162231445s
License | MR license check for Shoah victims? names took 0.4026780128479004s
License | HR license check for Shoah victims? names took 7.782317399978638s
Amount of data | Number of property check for Shoah victims? names took 0.1722707748413086s
Understandability | Number of label check for Shoah victims? names took 0.9224426746368408s
Understandability | URI regex check for Shoah victims? names took 0.4754009246826172s
Understandability | Vocabs check for Shoah victims? names took 0.1778864860534668s
Verifiability | Authors check for Shoah victims? names took 0.17769598960876465s
Verifiability | Publishers check for Shoah victims? names took 0.22386598587036133s
Performance | Throughput check for Shoah victims? names took 10.650736331939697s
Amount of data | Check the number of entities for Shoah victims? names took 8.392333984375e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.07777762413024902s
Interlinking | sameAs chians check for Shoah victims? names took 0.16674160957336426s
Interlinking | skos check for Shoah victims? names took 0.2920510768890381s
Interlinking | skos check for Shoah victims? names took 0.07246732711791992s
Timeliness | dataset update frequency check for Shoah victims? names took 0.3016386032104492s
Currency | Creation date check for Shoah victims? names took 0.19069218635559082s
Currency | Modification date check for Shoah victims? names took 0.32310914993286133s
Rep.Conc. | URIs length for Shoah victims? names took 2.503728151321411s
Interoperability | New vocabularies check for Shoah victims? names took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.1630861759185791s
Accuracy | Check Functional Property for Shoah victims? names took 0.12738513946533203s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.07329583168029785s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.5779566764831543s
Accuracy | Check White space in annotation for Shoah victims? names took 0.029102087020874023s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.02753591537475586s
Consistency | Disjoint class check for Shoah victims? names took 0.23121976852416992s
Consistency | Check Misplaced properties for Shoah victims? names took 1.986466884613037s
Consistency | Misplaced classes for Shoah victims? names took 0.2610628604888916s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5926322937011719s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.1636312007904053s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.0655677318573s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.030032634735107422s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.12027692794799805s
Security | Sign check for Shoah victims? names took 0.4620945453643799s
Availability | Check URIs Dereferenciability for Shoah victims? names took 2574.3226392269135s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 1.9013464450836182s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.021651506423950195s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.1920928955078125e-06s
Believability | Calculation of trust value for Shoah victims? names took 7.62939453125e-06s
INFO | --- Analysis for shoah-victims-names took 2684.433464050293s
Availability | SPARQL endpoint availability check for Person took 4.601478576660156e-05s
Availability | VoID file availability check for Person took 0.00035500526428222656s
Completeness | Calculation of interlinking completeness for Person took 0.2597930431365967s
Reputation | Calculation of the PageRank for Person took 0.023438215255737305s
Interlinking | Calculation of Degree of Connection for Person took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Person took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Person took 3.123283386230469e-05s
Believability | Calculation of trust value for Person took 8.344650268554688e-06s
INFO | --- Analysis for Shripriya_Dubey took 3.735793113708496s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.1961669921875e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.2552034854888916s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0010714530944824219s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.218650817871094e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 7.3909759521484375e-06s
INFO | --- Analysis for Shutterstock took 2.794999837875366s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.100799560546875e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2580418586730957s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.021228551864624023s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.504753112792969e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 7.867813110351562e-06s
INFO | --- Analysis for simile_data_collection took 3.40500807762146s
Availability | SPARQL endpoint availability check for SIMPLE took 4.315376281738281e-05s
Availability | VoID file availability check for SIMPLE took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.25033140182495117s
Reputation | Calculation of the PageRank for SIMPLE took 0.02096104621887207s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.0531158447265625e-05s
Believability | Calculation of trust value for SIMPLE took 7.867813110351562e-06s
INFO | --- Analysis for simple took 8.23371434211731s
Availability | SPARQL endpoint availability check for SITC-V4 took 27.027815580368042s
Availability | VoID file availability check for SITC-V4 took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.25507450103759766s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.6716461181640625e-05s
Believability | Calculation of trust value for SITC-V4 took 5.9604644775390625e-06s
INFO | --- Analysis for sitc-v4 took 127.13902759552002s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.506111145019531e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0003979206085205078s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.27300333976745605s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.1484832763671875e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 6.9141387939453125e-06s
INFO | --- Analysis for sli_galnet_rdf took 13.87959599494934s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.3392181396484375e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.25126051902770996s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.170967102050781e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 7.62939453125e-06s
INFO | --- Analysis for slideshare2rdf took 2.9844605922698975s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.267692565917969e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.2946016788482666s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.218650817871094e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 8.344650268554688e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.9407148361206055s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.7462754249572754s
Availability | VoID file availability check for Linked Stage Graph took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.2837531566619873s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.4836273193359375e-05s
Believability | Calculation of trust value for Linked Stage Graph took 8.58306884765625e-06s
INFO | --- Analysis for slod took 3.9551241397857666s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 5.793571472167969e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.2728273868560791s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020895004272460938s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.123283386230469e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 8.106231689453125e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 3.362269639968872s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.465120792388916s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0002770423889160156s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 122.3674533367157s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9932365417480469s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 8.79633617401123s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.589131355285645s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.2113347053528s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 3.3514654636383057s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.2479541301727295s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 9.589760303497314s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.25963521003723145s
License | MR license check for Smart Points Of Interest @PSNC took 0.5280561447143555s
License | HR license check for Smart Points Of Interest @PSNC took 300.1744339466095s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.3002336025238037s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.5234196186065674s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.776925802230835s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.5341053009033203s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.2017197608947754s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.2614426612854004s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.18799614906311s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 7.581710815429688e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.1965498924255371s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.2031688690185547s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4397470951080322s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4404575824737549s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 5.077509880065918s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.47340893745422363s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.21099019050598145s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 156.6371386051178s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.196181058883667s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.3803834915161133s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.35515737533569336s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 41.58881330490112s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.683015823364258s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.6234302520751953s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.210435152053833s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 82.95052862167358s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.463979721069336s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 34.73914837837219s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.2871949672698975s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 82.17546677589417s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7538421154022217s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.6262636184692383s
Security | Sign check for Smart Points Of Interest @PSNC took 1.0019912719726562s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 9.715574502944946s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 1.5517528057098389s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010132789611816406s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Smart_POI_dataset took 2275.727779150009s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.3029255867004395s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0007698535919189453s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.2524223327636719s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.5762786865234375e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 7.62939453125e-06s
INFO | --- Analysis for smartlink took 14.068365097045898s
Availability | SPARQL endpoint availability check for SNIK took 0.4854755401611328s
Availability | VoID file availability check for SNIK took 0.0006265640258789062s
Extra | Recovery of all triples for SNIK took 8.104586601257324s
Performance | Total latancy measurement for SNIK took 0.9741637706756592s
Amount of data | Number of triples check for SNIK took 0.21160888671875s
Interoperability | New terms check for SNIK took 1.362121343612671s
Versatility | Languages check for SNIK took 0.22983098030090332s
Interpretability | Number of blank nodes check for SNIK took 0.19919776916503906s
Interpretability | RDF structures check for SNIK took 0.1898043155670166s
Versatility | Serialization formats check for SNIK took 0.20904946327209473s
Availability | RDF dump link check for SNIK took 0.19581317901611328s
License | MR license check for SNIK took 0.21027326583862305s
License | HR license check for SNIK took 0.21949481964111328s
Amount of data | Number of property check for SNIK took 0.2133779525756836s
Understandability | Number of label check for SNIK took 0.21187233924865723s
Understandability | URI regex check for SNIK took 0.3948185443878174s
Understandability | Vocabs check for SNIK took 0.19305753707885742s
Verifiability | Authors check for SNIK took 0.19644427299499512s
Verifiability | Publishers check for SNIK took 0.20203185081481934s
Performance | Throughput check for SNIK took 11.463831663131714s
Amount of data | Check the number of entities for SNIK took 7.200241088867188e-05s
Verifiability | Contribs. check for SNIK took 0.20368719100952148s
Interlinking | sameAs chians check for SNIK took 0.2142643928527832s
Interlinking | skos check for SNIK took 0.1864030361175537s
Interlinking | skos check for SNIK took 0.21077942848205566s
Timeliness | dataset update frequency check for SNIK took 0.19626474380493164s
Currency | Creation date check for SNIK took 0.40627098083496094s
Currency | Modification date check for SNIK took 0.38369107246398926s
Rep.Conc. | URIs length for SNIK took 2.081641912460327s
Interoperability | New vocabularies check for SNIK took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.2175748348236084s
Accuracy | Check Functional Property for SNIK took 0.205963134765625s
Accuracy | Check Inverse Functional Property for SNIK took 0.19696712493896484s
Accuracy | Check Empty annotation labels for SNIK took 0.7767515182495117s
Accuracy | Check White space in annotation for SNIK took 0.027402877807617188s
Accuracy | Check Datatype consistency for SNIK took 0.2190852165222168s
Consistency | Disjoint class check for SNIK took 0.19632339477539062s
Consistency | Check Misplaced properties for SNIK took 0.6525330543518066s
Consistency | Misplaced classes for SNIK took 0.725250244140625s
Consistency | Check Ontology hijacking for SNIK took 1.751460313796997s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.1860480308532715s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.4570107460021973s
Conciseness | Check Extensional conciseness for SNIK took 0.1574573516845703s
Conciseness | Check Intensional conciseness for SNIK took 0.3100104331970215s
Security | Sign check for SNIK took 0.196638822555542s
Availability | Check URIs Dereferenciability for SNIK took 781.2690818309784s
Completeness | Calculation of interlinking completeness for SNIK took 0.862156867980957s
Reputation | Calculation of the PageRank for SNIK took 0.021415233612060547s
Interlinking | Calculation of Degree of Connection for SNIK took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.6689300537109375e-06s
Believability | Calculation of trust value for SNIK took 8.344650268554688e-06s
INFO | --- Analysis for snik took 843.481564283371s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.315376281738281e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.2698328495025635s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.24249267578125e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 8.58306884765625e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 4.698479652404785s
Availability | SPARQL endpoint availability check for SocialLink took 1.0473241806030273s
Availability | VoID file availability check for SocialLink took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for SocialLink took 0.26111841201782227s
Reputation | Calculation of the PageRank for SocialLink took 0.02122187614440918s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0008234977722167969s
Interlinking | Calculation of Clustering coefficient for SocialLink took 9.131431579589844e-05s
Believability | Calculation of trust value for SocialLink took 8.106231689453125e-06s
INFO | --- Analysis for SocialLink took 6.3100831508636475s
Availability | SPARQL endpoint availability check for SocialLink took 4.1961669921875e-05s
Availability | VoID file availability check for SocialLink took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for SocialLink took 0.30083131790161133s
Reputation | Calculation of the PageRank for SocialLink took 0.020748138427734375s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.0517578125e-05s
Believability | Calculation of trust value for SocialLink took 7.867813110351562e-06s
INFO | --- Analysis for sociallink took 4.2579686641693115s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.1961669921875e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2613096237182617s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020925283432006836s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.147125244140625e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 6.9141387939453125e-06s
INFO | --- Analysis for SocialRoles took 11.819620132446289s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.20327425003051758s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0008058547973632812s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 22.613206148147583s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.48542237281799316s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.25524401664733887s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.4243979454040527s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.4412243366241455s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.26027917861938477s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3765997886657715s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.10870504379272461s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.1380751132965088s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.821326494216919s
License | MR license check for Social Semantic Web Thesaurus took 0.13268017768859863s
License | HR license check for Social Semantic Web Thesaurus took 0.1131293773651123s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.1271834373474121s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.15555405616760254s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.19636058807373047s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.136918306350708s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.1340792179107666s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.11653566360473633s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.536122560501099s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.43865966796875e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12486934661865234s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.12883520126342773s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.12722182273864746s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.08098673820495605s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.09420919418334961s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.20801663398742676s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.21732783317565918s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 2.5649499893188477s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 4.206385612487793s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.14578557014465332s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.09934163093566895s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09434390068054199s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.536430835723877s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.01234889030456543s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.08849358558654785s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.3338940143585205s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.1035313606262207s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.324190139770508s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.4206721782684326s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00015997886657714844s
Security | Sign check for Social Semantic Web Thesaurus took 0.09563064575195312s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 113.83648371696472s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.7401788234710693s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.441375732421875e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.7228615283966064s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 256.9007420539856s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.34946346282958984s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.000270843505859375s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 119.07979393005371s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9601576328277588s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.044917583465576s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 13.788542747497559s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.1813313961029s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.232741355895996s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2633633613586426s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 12.233980655670166s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.32567477226257324s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.31723976135253906s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.23866295814514s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.41779017448425293s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.3286185264587402s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5827624797821045s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4327573776245117s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18394112586975098s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2464151382446289s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.233390808105469s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.605552673339844e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18260741233825684s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21386051177978516s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.46768712997436523s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4578208923339844s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 5.693525552749634s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5036811828613281s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21291708946228027s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 148.06321835517883s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21369600296020508s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.39489054679870605s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.24976491928100586s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 45.22030210494995s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.667377471923828s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.579301357269287s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.22239255905151367s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 83.17467451095581s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.321495056152344s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 39.202032804489136s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2962746620178223s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 86.65354776382446s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.756770372390747s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.601348876953125s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9665186405181885s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.038337469100952s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.3898885250091553s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.029399633407592773s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.00543212890625e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 6.198883056640625e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Soil_maps took 2273.812887907028s
Availability | SPARQL endpoint availability check for terrorrist ontology took 7.2479248046875e-05s
Availability | VoID file availability check for terrorrist ontology took 0.00033593177795410156s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.28016042709350586s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.886222839355469e-05s
Believability | Calculation of trust value for terrorrist ontology took 7.3909759521484375e-06s
INFO | --- Analysis for somya_omer took 4.18393611907959s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.220008850097656e-05s
Availability | VoID file availability check for Sonclubcx took 0.00032973289489746094s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.2626335620880127s
Reputation | Calculation of the PageRank for Sonclubcx took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.0728836059570312e-05s
Believability | Calculation of trust value for Sonclubcx took 7.62939453125e-06s
INFO | --- Analysis for sonclubcx took 5.874430179595947s
Availability | SPARQL endpoint availability check for SORS took 4.2438507080078125e-05s
Availability | VoID file availability check for SORS took 0.00037288665771484375s
Completeness | Calculation of interlinking completeness for SORS took 0.24614405632019043s
Reputation | Calculation of the PageRank for SORS took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for SORS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for SORS took 4.9114227294921875e-05s
Believability | Calculation of trust value for SORS took 1.7404556274414062e-05s
INFO | --- Analysis for sors took 14.27411937713623s
Availability | SPARQL endpoint availability check for Soudy České republiky took 6.0558319091796875e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.7285480499267578s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 2.9087066650390625e-05s
Believability | Calculation of trust value for Soudy České republiky took 7.62939453125e-06s
INFO | --- Analysis for soudy--esk--republiky took 4.259817600250244s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.220008850097656e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.2740316390991211s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 0.00010132789611816406s
Believability | Calculation of trust value for southampton-ac-uk took 1.2636184692382812e-05s
INFO | --- Analysis for southampton-ac-uk took 4.218279123306274s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 4.819439172744751s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.25321102142333984s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020984172821044922s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0517578125e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 7.152557373046875e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 12.198639154434204s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.482269287109375e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2656557559967041s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.021079301834106445s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.417533874511719e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 7.867813110351562e-06s
INFO | --- Analysis for southampton-ecs-eprints took 5.312242746353149s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5743026733398438s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00027251243591308594s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 217.7895679473877s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.267054796218872s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.095466136932373s
Interoperability | New terms check for Spanish Linguistic Datasets took 2.9968109130859375s
Versatility | Languages check for Spanish Linguistic Datasets took 44.255972146987915s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.0430223941802979s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.1447741985321045s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.26985859870910645s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.2729623317718506s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.26615214347839355s
License | MR license check for Spanish Linguistic Datasets took 0.25768303871154785s
License | HR license check for Spanish Linguistic Datasets took 0.35616016387939453s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.27470874786376953s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3038463592529297s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5151486396789551s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.2706446647644043s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.38492631912231445s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.26609015464782715s
Performance | Throughput check for Spanish Linguistic Datasets took 11.47800612449646s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 8.606910705566406e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.2890465259552002s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.26029515266418457s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2534446716308594s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2204759120941162s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.262725830078125s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5260157585144043s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5282013416290283s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 74.02014541625977s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2965207099914551s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.2656111717224121s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.26131486892700195s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.8671936988830566s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010036706924438477s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.7175633907318115s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.25692200660705566s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.654604196548462s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.406324863433838s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 70.40474581718445s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.3617346286773682s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.610519647598267s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.8954551219940186s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.26515936851501465s
Security | Sign check for Spanish Linguistic Datasets took 0.3813471794128418s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 11.75351881980896s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.8531622886657715s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.24249267578125e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 1.1920928955078125e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 7.62939453125e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 511.2326936721802s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.08582663536071777s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2548494338989258s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.482269287109375e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 7.152557373046875e-06s
INFO | --- Analysis for sparql-endpoint-status took 3.008953809738159s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 5.626678466796875e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.24793529510498047s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.9325485229492188e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 7.867813110351562e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 3.3332717418670654s
Availability | SPARQL endpoint availability check for SPQR took 4.172325134277344e-05s
Availability | VoID file availability check for SPQR took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for SPQR took 0.31899237632751465s
Reputation | Calculation of the PageRank for SPQR took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for SPQR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.956390380859375e-05s
Believability | Calculation of trust value for SPQR took 6.9141387939453125e-06s
INFO | --- Analysis for spqr took 3.9094080924987793s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.3392181396484375e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.24959826469421387s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.58306884765625e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.2159347534179688e-05s
INFO | --- Analysis for springernaturescigraph took 3.3534317016601562s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 5.936622619628906e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.6849887371063232s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 8.58306884765625e-06s
INFO | --- Analysis for srcmf took 9.987769842147827s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.6210274696350098s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.26279520988464355s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 4.57763671875e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 7.867813110351562e-06s
INFO | --- Analysis for ssf took 3.849738359451294s
Availability | SPARQL endpoint availability check for SSF took 4.1961669921875e-05s
Availability | VoID file availability check for SSF took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for SSF took 0.297527551651001s
Reputation | Calculation of the PageRank for SSF took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for SSF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SSF took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for SSF took 3.170967102050781e-05s
Believability | Calculation of trust value for SSF took 6.67572021484375e-06s
INFO | --- Analysis for ssf-lexicon took 3.0576934814453125s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.267692565917969e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.280353307723999s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.62396240234375e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 7.152557373046875e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.7060511112213135s
Availability | SPARQL endpoint availability check for STAC took 4.1961669921875e-05s
Availability | VoID file availability check for STAC took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for STAC took 0.2688710689544678s
Reputation | Calculation of the PageRank for STAC took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for STAC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for STAC took 3.0517578125e-05s
Believability | Calculation of trust value for STAC took 7.3909759521484375e-06s
INFO | --- Analysis for stac took 3.5999693870544434s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.172325134277344e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.25180673599243164s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.075599670410156e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 6.9141387939453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.9514966011047363s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.4345855712890625e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.26163578033447266s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.337860107421875e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 5.245208740234375e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.1838507652282715s
Availability | SPARQL endpoint availability check for Stammbuch took 4.220008850097656e-05s
Availability | VoID file availability check for Stammbuch took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2777225971221924s
Reputation | Calculation of the PageRank for Stammbuch took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 2.9325485229492188e-05s
Believability | Calculation of trust value for Stammbuch took 6.9141387939453125e-06s
INFO | --- Analysis for Stammbuch took 2.374896287918091s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.874079704284668s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.28160619735717773s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010347366333007812s
Believability | Calculation of trust value for statistics.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.6117331981658936s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 5.340576171875e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.00032138824462890625s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.25772905349731445s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.9802322387695312e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 6.9141387939453125e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.913590669631958s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2934844493865967s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010514259338378906s
Believability | Calculation of trust value for statusnet-1w6-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.9377100467681885s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 5.14984130859375e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.24351048469543457s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.580352783203125e-05s
Believability | Calculation of trust value for statusnet-20100-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-20100-org took 2.4363794326782227s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2629055976867676s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.794929504394531e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.6794650554656982s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 7.2479248046875e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2828714847564697s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 7.963180541992188e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.419095993041992s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.24936652183532715s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.632110595703125e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.6927719116210938e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.4496917724609375s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.27040648460388184s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011014938354492188s
Believability | Calculation of trust value for statusnet-bka-li took 7.62939453125e-06s
INFO | --- Analysis for statusnet-bka-li took 2.5267586708068848s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.29451560974121094s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.886222839355469e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.400709867477417s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 5.745887756347656e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2489180564880371s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.9114227294921875e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.8642218112945557s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.24785518646240234s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.1021575927734375e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.5600175857543945s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.26044273376464844s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020819664001464844s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011801719665527344s
Believability | Calculation of trust value for statusnet-chromic-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.493779182434082s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.935264587402344e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0007355213165283203s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2790086269378662s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.177757263183594e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.89249849319458s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 6.127357482910156e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2680995464324951s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.021294593811035156s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0010285377502441406s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 6.747245788574219e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.4888064861297607s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2850024700164795s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020899534225463867s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.914138793945312e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.306236982345581s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2404327392578125s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010132789611816406s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.5549869537353516s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.25548672676086426s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.4188804626464844s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2746145725250244s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.2928924560546875e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.621246337890625e-05s
INFO | --- Analysis for statusnet-doomicile-de took 3.275998592376709s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0007450580596923828s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2697944641113281s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020661354064941406s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.556510925292969e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-dtdns-net took 22.372201919555664s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.25121569633483887s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.600120544433594e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.369105339050293s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.2809140682220459s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 8.106231689453125e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.415456533432007s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.2675211429595947s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.250640869140625e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.38548231124878s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 5.555152893066406e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2424001693725586s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.021175861358642578s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.817413330078125e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.086862564086914s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.25601840019226074s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018286705017089844s
Believability | Calculation of trust value for statusnet-fragdev-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.2910897731781006s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.27772068977355957s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.414379119873047s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2387535572052002s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010561943054199219s
Believability | Calculation of trust value for statusnet-gegeweb-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.4069199562072754s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.26922082901000977s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02109360694885254s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.462501525878906e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-glou-org took 2.5630857944488525s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.935264587402344e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.269181489944458s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012755393981933594s
Believability | Calculation of trust value for statusnet-gomertronic-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.4509565830230713s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2532515525817871s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010514259338378906s
Believability | Calculation of trust value for statusnet-hackerposse-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.83020281791687s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2450106143951416s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.673004150390625e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.750131845474243s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2561225891113281s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 8.988380432128906e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.3776233196258545s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.24169921875s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.5228593349456787s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2730715274810791s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020838260650634766s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.076957702636719e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.5340702533721924s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 5.269050598144531e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.25931525230407715s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.3130202293396s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 5.650520324707031e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.25243639945983887s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02092123031616211s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0009500980377197266s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.0001270771026611328s
Believability | Calculation of trust value for statusnet-jonkman-ca took 7.62939453125e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.291341543197632s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.26970911026000977s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.1552734375e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 7.62939453125e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4919164180755615s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2627832889556885s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.3611056804656982s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.24832558631896973s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.981590270996094e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.3750076293945312s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.26418042182922363s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.534027099609375e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.3573176860809326s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.25985145568847656s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.57763671875e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.559795618057251s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.25432896614074707s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020661592483520508s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.079673767089844e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.596766948699951s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.27690553665161133s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.489059448242188e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.624346971511841s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 5.6743621826171875e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.28184056282043457s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011730194091796875s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.452812910079956s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.29327917098999023s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.808335542678833s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2535884380340576s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.0001010894775390625s
Believability | Calculation of trust value for statusnet-lydiastench-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.4208452701568604s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0012028217315673828s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2758018970489502s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.344864845275879s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.000457763671875s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2546813488006592s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.0001468658447265625s
Believability | Calculation of trust value for statusnet-macno-org took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-macno-org took 2.476233959197998s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.2553272247314453s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.4883151054382324s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 6.580352783203125e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.304610013961792s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02106952667236328s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0008580684661865234s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.797645568847656e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-maymay-net took 41.88268804550171s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.25050878524780273s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0015690326690673828s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.000164031982421875s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.4270994663238525s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 5.221366882324219e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.24498391151428223s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.989738464355469e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.491508722305298s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.274320125579834s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.350358486175537s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.2771930694580078s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020957469940185547s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.5291600227355957s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2857046127319336s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0009307861328125s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00013065338134765625s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.4983198642730713s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.27882909774780273s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.5488979816436768s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2597372531890869s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.7829537391662598s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.26966071128845215s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020834684371948242s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.559226989746094e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.514793872833252s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 5.340576171875e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2633075714111328s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.026899099349975586s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0012481212615966797s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-panda-id-au took 3.4927749633789062s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.26523518562316895s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.298324584960938e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.4164679050445557s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.28070592880249023s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020554780960083008s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.462501525878906e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.401136636734009s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2639939785003662s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.02056407928466797s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00023102760314941406s
Believability | Calculation of trust value for statusnet-postblue-info took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.445383310317993s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2687098979949951s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.319450378417969e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-progval-net took 2.5377209186553955s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.27919936180114746s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.868129014968872s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.27421998977661133s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.021191835403442383s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.2246954441070557s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.29116320610046387s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002155303955078125s
Believability | Calculation of trust value for statusnet-quitter-se took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-quitter-se took 3.5717029571533203s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.27696800231933594s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 9.965896606445312e-05s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.6575162410736084s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 0.0006551742553710938s
Availability | VoID file availability check for statusnet-recit-org took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.27626824378967285s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.936622619628906e-05s
Believability | Calculation of trust value for statusnet-recit-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-recit-org took 4.207926511764526s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 8.225440979003906e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.26682519912719727s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00014781951904296875s
Believability | Calculation of trust value for statusnet-russwurm-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.2011561393737793s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2585327625274658s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.177757263183594e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.682940721511841s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2570068836212158s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.296966552734375e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.5243425369262695s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2676970958709717s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02828526496887207s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.00011229515075683594s
Believability | Calculation of trust value for statusnet-scoffoni-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.393031120300293s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.29639363288879395s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.4611239433288574s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.2698550224304199s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.1523921489715576s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.26509642601013184s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00022268295288085938s
Believability | Calculation of trust value for statusnet-skilledtests-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 3.271929979324341s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 5.435943603515625e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.27330708503723145s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02045297622680664s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.0001049041748046875s
Believability | Calculation of trust value for statusnet-somsants-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.4432811737060547s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2706308364868164s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00015878677368164062s
Believability | Calculation of trust value for statusnet-soucy-cc took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.4230763912200928s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 6.031990051269531e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0006103515625s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2554280757904053s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-spip-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-spip-org took 3.3079018592834473s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2958197593688965s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.4142723083496094s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.270704984664917s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011229515075683594s
Believability | Calculation of trust value for statusnet-ssweeny-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.260608196258545s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.26995229721069336s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020345211029052734s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022101402282714844s
Believability | Calculation of trust value for statusnet-status-net took 1.7642974853515625e-05s
INFO | --- Analysis for statusnet-status-net took 3.388984203338623s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2560741901397705s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.4327282905578613s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 7.200241088867188e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.27318668365478516s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 8.96453857421875e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.4534733295440674s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.2579536437988281s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012135505676269531s
Believability | Calculation of trust value for statusnet-thelovebug-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.3629496097564697s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.27166199684143066s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-thornton2-com took 4.987907409667969s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.28448939323425293s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00011348724365234375s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.7200796604156494s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.000400543212890625s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.28531551361083984s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.910064697265625e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.4868714809417725s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2698638439178467s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.565086841583252s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.26644062995910645s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.520240068435669s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.363059997558594e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.28215909004211426s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for steak took 3.6338024139404297s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.2438507080078125e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2509939670562744s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020245075225830078s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.4836273193359375e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.1920928955078125e-05s
INFO | --- Analysis for stitch-rameau took 3.9139797687530518s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.61482834815979s
Availability | VoID file availability check for Stone Tech Square took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.269031286239624s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.239776611328125e-05s
Believability | Calculation of trust value for Stone Tech Square took 8.58306884765625e-06s
INFO | --- Analysis for stone-tech-square-data took 4.420243978500366s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.1484832763671875e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.27045273780822754s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 2.8848648071289062e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.62939453125e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 3.015308380126953s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.4655113220214844s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0013222694396972656s
Extra | Recovery of all triples for STW Thesaurus for Economics took 0.23970580101013184s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.2139403820037842s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6521878242492676s
Interoperability | New terms check for STW Thesaurus for Economics took 1.4084677696228027s
Versatility | Languages check for STW Thesaurus for Economics took 1.4792606830596924s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5155184268951416s
Security | Check HTTPS for STW Thesaurus for Economics took 0.12790608406066895s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.24161005020141602s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.27949070930480957s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.22655606269836426s
License | MR license check for STW Thesaurus for Economics took 0.23546385765075684s
License | HR license check for STW Thesaurus for Economics took 2.0351598262786865s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2477712631225586s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6153852939605713s
Understandability | URI regex check for STW Thesaurus for Economics took 0.47568464279174805s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.22374987602233887s
Verifiability | Authors check for STW Thesaurus for Economics took 0.27382612228393555s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2671494483947754s
Performance | Throughput check for STW Thesaurus for Economics took 11.071600914001465s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 8.559226989746094e-05s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2823524475097656s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.24169683456420898s
Interlinking | skos check for STW Thesaurus for Economics took 0.3611180782318115s
Interlinking | skos check for STW Thesaurus for Economics took 0.28389763832092285s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.24322772026062012s
Currency | Creation date check for STW Thesaurus for Economics took 0.4662156105041504s
Currency | Modification date check for STW Thesaurus for Economics took 0.5126047134399414s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.2083375453948975s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 38.35786581039429s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2739522457122803s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2776932716369629s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.26662540435791016s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 13.144126892089844s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0656931400299072s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.26430654525756836s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2596828937530518s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.7840073108673096s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.23154878616333s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 0.00015282630920410156s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.24624919891357422s
Security | Sign check for STW Thesaurus for Economics took 0.23503470420837402s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2788.6514756679535s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 1.6630589962005615s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.0265505313873291s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00011944770812988281s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 7.910630941390991s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.049041748046875e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 2912.54639339447s
Availability | SPARQL endpoint availability check for SudershanTech took 4.315376281738281e-05s
Availability | VoID file availability check for SudershanTech took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.28624439239501953s
Reputation | Calculation of the PageRank for SudershanTech took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.504753112792969e-05s
Believability | Calculation of trust value for SudershanTech took 7.152557373046875e-06s
INFO | --- Analysis for SudershanTech took 2.8170504570007324s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 1.0730175971984863s
Availability | VoID file availability check for Sudoc bibliographic data took 0.00032639503479003906s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.7125077247619629s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 5.3882598876953125e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 6.9141387939453125e-06s
INFO | --- Analysis for sudocfr took 9.05421757698059s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 307.1485278606415s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0015227794647216797s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 2.4261116981506348s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.021574735641479492s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0009865760803222656s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 9.322166442871094e-05s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 8.106231689453125e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 2227.617592573166s
Availability | SPARQL endpoint availability check for Surge Radio took 4.696846008300781e-05s
Availability | VoID file availability check for Surge Radio took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.2854793071746826s
Reputation | Calculation of the PageRank for Surge Radio took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 9.34600830078125e-05s
Believability | Calculation of trust value for Surge Radio took 7.867813110351562e-06s
INFO | --- Analysis for surge-radio took 7.6535255908966064s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.363059997558594e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.2539784908294678s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.02035689353942871s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.0040740966796875e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 7.3909759521484375e-06s
INFO | --- Analysis for SWAT took 19.898348093032837s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.267692565917969e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4903883934020996s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2697422504425049s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.021080732345581055s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0008816719055175781s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 8.177757263183594e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 7.152557373046875e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.595666408538818s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.3683953285217285s
Availability | VoID file availability check for SweFN-RDF took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2664806842803955s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.021029233932495117s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.457069396972656e-05s
Believability | Calculation of trust value for SweFN-RDF took 8.106231689453125e-06s
INFO | --- Analysis for swefn-rdf took 7.0602967739105225s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.458427429199219e-05s
Availability | VoID file availability check for SwetoDblp took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.27014994621276855s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020731449127197266s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0009617805480957031s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 5.030632019042969e-05s
Believability | Calculation of trust value for SwetoDblp took 7.867813110351562e-06s
INFO | --- Analysis for sweto-dblp took 23.146969318389893s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.6422431468963623s
Availability | VoID file availability check for Swift Vocabulary took 0.0005085468292236328s
Extra | Recovery of all triples for Swift Vocabulary took 2.0591955184936523s
Performance | Total latancy measurement for Swift Vocabulary took 1.0768201351165771s
Amount of data | Number of triples check for Swift Vocabulary took 0.2121570110321045s
Interoperability | New terms check for Swift Vocabulary took 1.3839881420135498s
Versatility | Languages check for Swift Vocabulary took 0.17586994171142578s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.17954158782958984s
Interpretability | RDF structures check for Swift Vocabulary took 0.18787217140197754s
Versatility | Serialization formats check for Swift Vocabulary took 0.17860770225524902s
Availability | RDF dump link check for Swift Vocabulary took 0.16048812866210938s
License | MR license check for Swift Vocabulary took 0.1778402328491211s
License | HR license check for Swift Vocabulary took 0.17453336715698242s
Amount of data | Number of property check for Swift Vocabulary took 0.19485950469970703s
Understandability | Number of label check for Swift Vocabulary took 0.18130087852478027s
Understandability | URI regex check for Swift Vocabulary took 0.3456871509552002s
Understandability | Vocabs check for Swift Vocabulary took 0.15964078903198242s
Verifiability | Authors check for Swift Vocabulary took 0.15901565551757812s
Verifiability | Publishers check for Swift Vocabulary took 0.17646312713623047s
Performance | Throughput check for Swift Vocabulary took 11.010570764541626s
Amount of data | Check the number of entities for Swift Vocabulary took 0.00015282630920410156s
Verifiability | Contribs. check for Swift Vocabulary took 0.16123199462890625s
Interlinking | sameAs chians check for Swift Vocabulary took 0.19448614120483398s
Interlinking | skos check for Swift Vocabulary took 0.1741471290588379s
Interlinking | skos check for Swift Vocabulary took 0.2281942367553711s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.17690563201904297s
Currency | Creation date check for Swift Vocabulary took 0.3508594036102295s
Currency | Modification date check for Swift Vocabulary took 0.4091832637786865s
Rep.Conc. | URIs length for Swift Vocabulary took 0.7850680351257324s
Interoperability | New vocabularies check for Swift Vocabulary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.21124815940856934s
Accuracy | Check Functional Property for Swift Vocabulary took 0.228926420211792s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.23070907592773438s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.37447214126586914s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0037844181060791016s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03646039962768555s
Consistency | Disjoint class check for Swift Vocabulary took 0.18943166732788086s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.42228055000305176s
Consistency | Misplaced classes for Swift Vocabulary took 0.28632402420043945s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.4587266445159912s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.201439619064331s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.433873176574707s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.027255535125732422s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.18325161933898926s
Security | Sign check for Swift Vocabulary took 0.17273640632629395s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 1025.6155679225922s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.7760279178619385s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.021604537963867188s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 7.653236389160156e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.6689300537109375e-06s
Believability | Calculation of trust value for Swift Vocabulary took 7.867813110351562e-06s
INFO | --- Analysis for Swift took 1071.0696187019348s
Availability | SPARQL endpoint availability check for SymbolicData took 4.267692565917969e-05s
Availability | VoID file availability check for SymbolicData took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.6993355751037598s
Reputation | Calculation of the PageRank for SymbolicData took 0.02075791358947754s
Interlinking | Calculation of Degree of Connection for SymbolicData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.218650817871094e-05s
Believability | Calculation of trust value for SymbolicData took 8.58306884765625e-06s
INFO | --- Analysis for symbolicdata took 4.26573920249939s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.506111145019531e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0014815330505371094s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.2442159652709961s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020978689193725586s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.1948089599609375e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 7.152557373046875e-06s
INFO | --- Analysis for symptoms-in-chinese took 53.32116675376892s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.4936797618865967s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0004763603210449219s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.49628591537475586s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8450889587402344s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 50.251044034957886s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 21.243387937545776s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.18220281600952148s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 8.557035446166992s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.11901640892028809s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.7956814765930176s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.7375278472900391s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.15739750862121582s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.4212958812713623s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.87772250175476s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5280570983886719s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 38.53663659095764s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3549830913543701s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.19883513450622559s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.1799178123474121s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 1.1984941959381104s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.39791202545166s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 6.890296936035156e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.6618866920471191s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 2.1789443492889404s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.568730354309082s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.4788854122161865s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.4641666412353516s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.0421273708343506s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.837822675704956s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 66.25888228416443s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.18398046493530273s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2598252296447754s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0012493133544921875s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0015788078308105469s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.1951460838317871s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.65356683731079s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2600226402282715s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.4352118968963623s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.1696696281433105s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.60351252555847s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002229452133178711s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.3275449275970459s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.173506498336792s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 12.142521619796753s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.9821114540100098s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.021085262298583984s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 8.106231689453125e-06s
INFO | --- Analysis for sztaki-lod took 486.0251798629761s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.76837158203125e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.25733160972595215s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.459785461425781e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 7.152557373046875e-06s
INFO | --- Analysis for t4gm-info took 7.780492544174194s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.291534423828125e-05s
Availability | VoID file availability check for tags2con delicious took 0.0010528564453125s
Completeness | Calculation of interlinking completeness for tags2con delicious took 1.4209961891174316s
Reputation | Calculation of the PageRank for tags2con delicious took 0.021373748779296875s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.887580871582031e-05s
Believability | Calculation of trust value for tags2con delicious took 1.2159347534179688e-05s
INFO | --- Analysis for tags2con-delicious took 846.9385952949524s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.9015600681305s
Availability | VoID file availability check for Taiwan geographic names took 0.0008366107940673828s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.8429045677185059s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.021181344985961914s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 9.059906005859375e-05s
Believability | Calculation of trust value for Taiwan geographic names took 8.344650268554688e-06s
INFO | --- Analysis for taiwan-geographic-names took 670.3717076778412s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.839897155761719e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.7162585258483887s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.179115295410156e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 8.106231689453125e-06s
INFO | --- Analysis for talis-openlibrary took 25.96173667907715s
Availability | SPARQL endpoint availability check for TalkBank took 4.267692565917969e-05s
Availability | VoID file availability check for TalkBank took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for TalkBank took 0.6881787776947021s
Reputation | Calculation of the PageRank for TalkBank took 0.020946741104125977s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for TalkBank took 3.218650817871094e-05s
Believability | Calculation of trust value for TalkBank took 7.867813110351562e-06s
INFO | --- Analysis for talkbank took 4.192483425140381s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9523293972015381s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.2689199447631836s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012063980102539062s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for taxonconcept took 14.653746604919434s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.3392181396484375e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.28467416763305664s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.20159912109375e-05s
Believability | Calculation of trust value for taxonconcept-assets took 7.152557373046875e-06s
INFO | --- Analysis for taxonconcept-assets took 3.238393545150757s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.506111145019531e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.27335071563720703s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.221366882324219e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 8.106231689453125e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.8282604217529297s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 1.9767265319824219s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.27602624893188477s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.839897155761719e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 7.867813110351562e-06s
INFO | --- Analysis for taxref-ld took 7.280425548553467s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.5581238269806s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.000701904296875s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.38969969749450684s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.790855407714844e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 7.3909759521484375e-06s
INFO | --- Analysis for tcga took 540.9094367027283s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3782768249511719s
Availability | VoID file availability check for TCGA Roadmap took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.7029390335083008s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 8.153915405273438e-05s
Believability | Calculation of trust value for TCGA Roadmap took 8.106231689453125e-06s
INFO | --- Analysis for tcga-roadmap took 6.648693084716797s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.4711370468139648s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3358340263366699s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 9.799003601074219e-05s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.152557373046875e-06s
INFO | --- Analysis for tcmgenedit_dataset took 142.36514568328857s
Availability | SPARQL endpoint availability check for TDS took 4.220008850097656e-05s
Availability | VoID file availability check for TDS took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for TDS took 0.2838408946990967s
Reputation | Calculation of the PageRank for TDS took 0.02172994613647461s
Interlinking | Calculation of Degree of Connection for TDS took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for TDS took 5.1021575927734375e-05s
Believability | Calculation of trust value for TDS took 8.344650268554688e-06s
INFO | --- Analysis for tds took 6.716939449310303s
Availability | SPARQL endpoint availability check for TED Talks took 8.416175842285156e-05s
Availability | VoID file availability check for TED Talks took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for TED Talks took 0.7100315093994141s
Reputation | Calculation of the PageRank for TED Talks took 0.020868778228759766s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for TED Talks took 3.2901763916015625e-05s
Believability | Calculation of trust value for TED Talks took 8.344650268554688e-06s
INFO | --- Analysis for ted-talks took 3.3745174407958984s
Availability | SPARQL endpoint availability check for TEKORD took 4.3392181396484375e-05s
Availability | VoID file availability check for TEKORD took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2720797061920166s
Reputation | Calculation of the PageRank for TEKORD took 0.020939350128173828s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.839897155761719e-05s
Believability | Calculation of trust value for TEKORD took 7.62939453125e-06s
INFO | --- Analysis for tekord took 5.645045757293701s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.4214723110198975s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.25501418113708496s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0008285045623779297s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00011515617370605469s
Believability | Calculation of trust value for Telegraphis Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for telegraphis took 8.443233728408813s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.267692565917969e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.2692244052886963s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.985664367675781e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 7.152557373046875e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.553441286087036s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.100799560546875e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.260040283203125s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.021060943603515625s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.9583170413970947s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2572286128997803s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for terminesp took 2.8187320232391357s
Availability | SPARQL endpoint availability check for Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology took 0.0008387565612792969s
Completeness | Calculation of interlinking completeness for Ontology took 0.2669863700866699s
Reputation | Calculation of the PageRank for Ontology took 0.020735502243041992s
Interlinking | Calculation of Degree of Connection for Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for Ontology took 7.62939453125e-06s
INFO | --- Analysis for Terrorist_attack took 2.8669791221618652s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.315376281738281e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.25944018363952637s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.719329833984375e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 7.152557373046875e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.3264708518981934s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.100799560546875e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.2860381603240967s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.021090984344482422s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 3.0994415283203125e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.62939453125e-06s
INFO | --- Analysis for tesauro-materias-bupm took 3.0176122188568115s
Availability | SPARQL endpoint availability check for Teseo took 4.1484832763671875e-05s
Availability | VoID file availability check for Teseo took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Teseo took 0.26880693435668945s
Reputation | Calculation of the PageRank for Teseo took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Teseo took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0010268688201904297s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.695487976074219e-05s
Believability | Calculation of trust value for Teseo took 7.62939453125e-06s
INFO | --- Analysis for teseo took 2.8499808311462402s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 5.7220458984375e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0008046627044677734s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.24088144302368164s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.0517578125e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 7.62939453125e-06s
INFO | --- Analysis for Tesla_Deaths took 4.358353853225708s
Availability | SPARQL endpoint availability check for test took 5.698204040527344e-05s
Availability | VoID file availability check for test took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for test took 0.2638387680053711s
Reputation | Calculation of the PageRank for test took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for test took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for test took 2.9802322387695312e-05s
Believability | Calculation of trust value for test took 1.2159347534179688e-05s
INFO | --- Analysis for test took 2.3647499084472656s
Availability | SPARQL endpoint availability check for Test took 4.3392181396484375e-05s
Availability | VoID file availability check for Test took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Test took 0.26410388946533203s
Reputation | Calculation of the PageRank for Test took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for Test took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Test took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Test took 3.075599670410156e-05s
Believability | Calculation of trust value for Test took 7.62939453125e-06s
INFO | --- Analysis for Test took 2.355008840560913s
Availability | SPARQL endpoint availability check for test-svu took 20.203872680664062s
Availability | VoID file availability check for test-svu took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for test-svu took 0.2794680595397949s
Reputation | Calculation of the PageRank for test-svu took 0.021731138229370117s
Interlinking | Calculation of Degree of Connection for test-svu took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.218650817871094e-05s
Believability | Calculation of trust value for test-svu took 8.106231689453125e-06s
INFO | --- Analysis for test-svu took 52.61791157722473s
Availability | SPARQL endpoint availability check for Test took 4.267692565917969e-05s
Availability | VoID file availability check for Test took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Test took 0.268949031829834s
Reputation | Calculation of the PageRank for Test took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Test took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Test took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Test took 2.9325485229492188e-05s
Believability | Calculation of trust value for Test took 7.152557373046875e-06s
INFO | --- Analysis for Test_ took 2.853652238845825s
Availability | SPARQL endpoint availability check for xxxxx took 261.1565651893616s
Availability | VoID file availability check for xxxxx took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for xxxxx took 0.7617132663726807s
Reputation | Calculation of the PageRank for xxxxx took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for xxxxx took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for xxxxx took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.315376281738281e-05s
Believability | Calculation of trust value for xxxxx took 7.3909759521484375e-06s
INFO | --- Analysis for testee took 798.2691054344177s
Availability | SPARQL endpoint availability check for Texai Lexicon took 5.1021575927734375e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.7005932331085205s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020871639251708984s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.1948089599609375e-05s
Believability | Calculation of trust value for Texai Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for texai_lexicon took 7.480601787567139s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.410743713378906e-05s
Availability | VoID file availability check for tharawat magazine took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.2572476863861084s
Reputation | Calculation of the PageRank for tharawat magazine took 0.020863056182861328s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00011372566223144531s
Believability | Calculation of trust value for tharawat magazine took 7.867813110351562e-06s
INFO | --- Analysis for tharawat-magazine-com took 4.364458322525024s
Availability | SPARQL endpoint availability check for The CIARD RING took 5.269050598144531e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.26439690589904785s
Reputation | Calculation of the PageRank for The CIARD RING took 0.021019458770751953s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.218650817871094e-05s
Believability | Calculation of trust value for The CIARD RING took 8.58306884765625e-06s
INFO | --- Analysis for the-ciard-ring took 3.3871288299560547s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.17596220970153809s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.7032945156097412s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.02084517478942871s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 5.53131103515625e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 8.344650268554688e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 3.9082064628601074s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.8783073425292969s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007307529449462891s
Extra | Recovery of all triples for The European Library Open Dataset took 1.4772183895111084s
Performance | Total latancy measurement for The European Library Open Dataset took 1.3234572410583496s
Amount of data | Number of triples check for The European Library Open Dataset took 30.226868391036987s
Versatility | Languages check for The European Library Open Dataset took 0.31151461601257324s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.186400175094604s
Interpretability | RDF structures check for The European Library Open Dataset took 0.2528078556060791s
Versatility | Serialization formats check for The European Library Open Dataset took 0.2799670696258545s
Availability | RDF dump link check for The European Library Open Dataset took 0.2450261116027832s
License | MR license check for The European Library Open Dataset took 0.272921085357666s
License | HR license check for The European Library Open Dataset took 0.23793959617614746s
Amount of data | Number of property check for The European Library Open Dataset took 0.24755454063415527s
Understandability | Number of label check for The European Library Open Dataset took 1.30985689163208s
Understandability | URI regex check for The European Library Open Dataset took 0.46988654136657715s
Understandability | Vocabs check for The European Library Open Dataset took 0.22062444686889648s
Verifiability | Authors check for The European Library Open Dataset took 0.2794680595397949s
Verifiability | Publishers check for The European Library Open Dataset took 0.2464618682861328s
Performance | Throughput check for The European Library Open Dataset took 11.30703592300415s
Amount of data | Check the number of entities for The European Library Open Dataset took 6.937980651855469e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.2758922576904297s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.2829868793487549s
Interlinking | skos check for The European Library Open Dataset took 0.2794661521911621s
Interlinking | skos check for The European Library Open Dataset took 0.2769169807434082s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.2797970771789551s
Currency | Creation date check for The European Library Open Dataset took 0.5081744194030762s
Currency | Modification date check for The European Library Open Dataset took 0.5014634132385254s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.55760073661804s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.25072240829467773s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.47264814376831055s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.027910947799682617s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02793574333190918s
Consistency | Disjoint class check for The European Library Open Dataset took 0.21241068840026855s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.420591354370117s
Consistency | Misplaced classes for The European Library Open Dataset took 0.3531224727630615s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.6756682395935059s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.1533849239349365s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.392982721328735s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03522682189941406s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.27920103073120117s
Security | Sign check for The European Library Open Dataset took 0.26627492904663086s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 12.563274145126343s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 1.4471509456634521s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.365776062011719e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for the-european-library-open-dataset took 400.6904082298279s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.058265686035156s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.7070140838623047s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00011444091796875s
Believability | Calculation of trust value for The Eurostat Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for the-eurostat-linked-data took 244.00748777389526s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.2438507080078125e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.25763678550720215s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.021348237991333008s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 2.9087066650390625e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.3909759521484375e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 3.881863594055176s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 5.054473876953125e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2614719867706299s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.021054506301879883s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 8.273124694824219e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 8.344650268554688e-06s
INFO | --- Analysis for the-living-lod-cloud took 43.798943519592285s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.3392181396484375e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.2773857116699219s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020948171615600586s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.2901763916015625e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 7.62939453125e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.7818140983581543s
Availability | SPARQL endpoint availability check for The View From took 0.08673429489135742s
Availability | VoID file availability check for The View From took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for The View From took 0.24124550819396973s
Reputation | Calculation of the PageRank for The View From took 0.021754026412963867s
Interlinking | Calculation of Degree of Connection for The View From took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for The View From took 0.0008549690246582031s
Interlinking | Calculation of Clustering coefficient for The View From took 9.274482727050781e-05s
Believability | Calculation of trust value for The View From took 8.58306884765625e-06s
INFO | --- Analysis for the-view-from took 2.937422037124634s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.38194251060486s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.7620425224304199s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.021183252334594727s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.24249267578125e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 9.5367431640625e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 74.53494954109192s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.006406545639038s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.25320935249328613s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 0.00011396408081054688s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.0517578125e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 7.62939453125e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.74756407737732s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.363059997558594e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.25937604904174805s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.0216219425201416s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0010211467742919922s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.0001232624053955078s
Believability | Calculation of trust value for The Content Wrangler took 7.867813110351562e-06s
INFO | --- Analysis for thecontentwrangler-com took 2.93219256401062s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.172325134277344e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.26312875747680664s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.075599670410156e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 1.2159347534179688e-05s
INFO | --- Analysis for thesaurus-bncf took 2.873948097229004s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.3392181396484375e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.27646684646606445s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 2.9802322387695312e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 7.152557373046875e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.489617347717285s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.4805111885070801s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0012500286102294922s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.2460956573486328s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.021132946014404297s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.772445678710938e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 6.4373016357421875e-06s
INFO | --- Analysis for thesaurus-w took 3.95870041847229s
Availability | SPARQL endpoint availability check for theses.fr took 4.315376281738281e-05s
Availability | VoID file availability check for theses.fr took 0.000335693359375s
Completeness | Calculation of interlinking completeness for theses.fr took 0.27201080322265625s
Reputation | Calculation of the PageRank for theses.fr took 0.0213468074798584s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.1021575927734375e-05s
Believability | Calculation of trust value for theses.fr took 1.33514404296875e-05s
INFO | --- Analysis for thesesfr took 4.783291578292847s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 5.269050598144531e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.2690598964691162s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.600120544433594e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 7.3909759521484375e-06s
INFO | --- Analysis for Thinkphile took 2.3996827602386475s
Availability | SPARQL endpoint availability check for ThIST took 264.5889501571655s
Availability | VoID file availability check for ThIST took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for ThIST took 0.24937009811401367s
Reputation | Calculation of the PageRank for ThIST took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for ThIST took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for ThIST took 7.843971252441406e-05s
Believability | Calculation of trust value for ThIST took 6.9141387939453125e-06s
INFO | --- Analysis for thist took 563.9626035690308s
Availability | SPARQL endpoint availability check for TIP took 40.039119243621826s
Availability | VoID file availability check for TIP took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for TIP took 0.7702674865722656s
Reputation | Calculation of the PageRank for TIP took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for TIP took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for TIP took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011730194091796875s
Believability | Calculation of trust value for TIP took 7.62939453125e-06s
INFO | --- Analysis for tip took 104.50827646255493s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.267692565917969e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.2575209140777588s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.020870447158813477s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.0517578125e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 7.152557373046875e-06s
INFO | --- Analysis for TOPMODEL took 21.963202953338623s
Availability | SPARQL endpoint availability check for Tourpedia took 4.076957702636719e-05s
Availability | VoID file availability check for Tourpedia took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.2640116214752197s
Reputation | Calculation of the PageRank for Tourpedia took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for Tourpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 2.9325485229492188e-05s
Believability | Calculation of trust value for Tourpedia took 8.106231689453125e-06s
INFO | --- Analysis for tourpedia took 5.5003509521484375s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 4.417283773422241s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.6877844333648682s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.552436828613281e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 7.867813110351562e-06s
INFO | --- Analysis for TP-data took 11.166572093963623s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 1.6525790691375732s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.00037169456481933594s
Extra | Recovery of all triples for Trackloaded Linked Open Data took 1.9267470836639404s
Performance | Total latancy measurement for Trackloaded Linked Open Data took 2.0490756034851074s
Amount of data | Number of triples check for Trackloaded Linked Open Data took 1.7303853034973145s
Interoperability | New terms check for Trackloaded Linked Open Data took 2.9360146522521973s
Versatility | Languages check for Trackloaded Linked Open Data took 1.7754971981048584s
Interpretability | Number of blank nodes check for Trackloaded Linked Open Data took 1.5552194118499756s
Interpretability | RDF structures check for Trackloaded Linked Open Data took 1.7436473369598389s
Versatility | Serialization formats check for Trackloaded Linked Open Data took 1.5188891887664795s
Availability | RDF dump link check for Trackloaded Linked Open Data took 1.6977238655090332s
License | MR license check for Trackloaded Linked Open Data took 1.6583375930786133s
License | HR license check for Trackloaded Linked Open Data took 1.5302631855010986s
Amount of data | Number of property check for Trackloaded Linked Open Data took 1.5510153770446777s
Understandability | Number of label check for Trackloaded Linked Open Data took 1.5316271781921387s
Understandability | URI regex check for Trackloaded Linked Open Data took 3.305345058441162s
Understandability | Vocabs check for Trackloaded Linked Open Data took 1.7725822925567627s
Verifiability | Authors check for Trackloaded Linked Open Data took 1.4421250820159912s
Verifiability | Publishers check for Trackloaded Linked Open Data took 1.7601428031921387s
Performance | Throughput check for Trackloaded Linked Open Data took 20.084848403930664s
Amount of data | Check the number of entities for Trackloaded Linked Open Data took 3.8623809814453125e-05s
Verifiability | Contribs. check for Trackloaded Linked Open Data took 1.6472725868225098s
Interlinking | sameAs chians check for Trackloaded Linked Open Data took 1.547339677810669s
Interlinking | skos check for Trackloaded Linked Open Data took 1.7262516021728516s
Interlinking | skos check for Trackloaded Linked Open Data took 0.1010892391204834s
Timeliness | dataset update frequency check for Trackloaded Linked Open Data took 1.741729974746704s
Currency | Creation date check for Trackloaded Linked Open Data took 5.217189788818359s
Currency | Modification date check for Trackloaded Linked Open Data took 3.1530256271362305s
Rep.Conc. | URIs length for Trackloaded Linked Open Data took 3.7029614448547363s
Interoperability | New vocabularies check for Trackloaded Linked Open Data took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Trackloaded Linked Open Data took 1.5652830600738525s
Consistency | Disjoint class check for Trackloaded Linked Open Data took 1.2177503108978271s
Consistency | Check Misplaced properties for Trackloaded Linked Open Data took 3.0291762351989746s
Consistency | Check Ontology hijacking for Trackloaded Linked Open Data took 2.8479435443878174s
Consistency | Check Invalid usage of undefined properties for Trackloaded Linked Open Data took 1.4808845520019531s
Security | Sign check for Trackloaded Linked Open Data took 1.5438079833984375s
Availability | Check URIs Dereferenciability for Trackloaded Linked Open Data took 1.4536633491516113s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.2663154602050781s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Linked Open Data took 2.384185791015625e-06s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 7.152557373046875e-06s
